This is not a "good" thing, in my opinion. There are a lot of features in postgres 8.0, 8.1 and 8.2 which we *should* make available to end users (and even enforce in some cases).
Dropping support for old dependencies is a very good thing and hell knows how much fire this sort of thing started in Django before (cf python2.3 support). I strongly recommend fully dropping support for 8.0 for 1.3 or 1.4, and drop support for 8.1 in the following release. As was stated before, 8.3 is usually the oldest version users are running. On Thu, Jun 10, 2010 at 5:29 PM, Russell Keith-Magee <russ...@keith-magee.com> wrote: > On Thu, Jun 10, 2010 at 4:21 PM, si...@2ndquadrant.com > <si...@2ndquadrant.com> wrote: >> >> On Jun 10, 6:53 am, Paul McMillan <p...@mcmillan.ws> wrote: >>> +1 for option 2. >>> >>> Changing 1.2 behavior now seems like a bad idea, and Jacob's arguments >>> are good. >> >> Jacob's arguments are good; I would suggest Django goes further still. >> >> PostgreSQL... >> 7.4 and 8.0 are slated for de-support as soon as 9.0 is released >> (soon). >> 8.1 is due to be de-supported about 4 months after release of 9.0 (end >> of 2010). >> 8.2 support is due to last until the end of 2011. >> >> There's a common misconception that the 8.x releases are somehow all >> fairly similar, which is not really the case. They're all major >> releases in their own right and need to be discussed separately. >> >> On top of that, 8.2 is the earliest release that has simplified file- >> based replication. 8.3 and 8.4 are the releases to recommend for >> people who want decent performance. 8.3 also has some changes to >> default casting between text and other datatypes which can cause some >> earlier SQL to fail. >> >> I would ask Django to move directly to 8.3 as minimum supported >> version. That's the lowest release I've seen anyone use myself lately. >> Current stable release is 8.4, which is the long term support version >> now in later distros. 9.0 is due out shortly. >> >> Happy to help if issues arise. > > There appears to be some confusion here. We're not recommending a > version of PostgreSQL that end-users should use; we're nominating the > minimum possible version that passes Django's test suite. PostgreSQL > 7.4 may be bad for all sorts of reasons, but right now, all the > features of PostgreSQL that Django uses utilize are available in > PostgreSQL 7.4. When the fix for #8901 lands, this raises the bar to > PostgreSQL 8.0, but only because of the use of > pg_get_serial_sequence(). > > I completely agree that users would be well advised to upgrade to > PostreSQL 8.4, and there are many reasons beyond basic Django > compatibility that should drive that upgrading process. However, that > doesn't change the fact that from a purely functional perspective, > Django will work happily on PostgreSQL 8.0 (unless you want to use > database-level autocommit or savepoints, in which case the minimum > version is 8.2). > > Yours, > Russ Magee %-) > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-develop...@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
