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. -- Simon Riggs www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Training and Services -- 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.
