On Thu, 2010-06-10 at 13:41 +0400, reg...@messir.net wrote: > For old postgress we have old django. So, do not hesitate kicking off > old code. Even 8.2 version is very-very old so it's okay to depend on > 8.2+. > > > While we support PostgreSQL, our documentation doesn't actually > > specify a minimum supported version. We have a couple of features that > > are no-ops for versions prior to 8.2 (savepoints and database > > autocommit), but we don't actually document a minimum required > > version.
(Re-post, first post stalled) Yeh, Django should really be moving to PostgreSQL 8.3 or above, because of performance, administrative ease and availability of replication features. PostgreSQL 7.4 and 8.0 are due to be de-supported in about 1 month, 8.1 is due for de-support by end of 2010. (8.0 and 8.1 have already been de-supported on Windows). So 8.2 is the minimum sensible version for next release of Django, though 8.3 should be minimum recommended with 8.4 current stable release as dev target. Happy to help with any issues arising from that move. -- 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.
