On Thu, 2010-06-10 at 22:29 +0800, Russell Keith-Magee wrote: > 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).
I take your point about the differences. In this case, the PostgreSQL project is just about to de-support those release levels, so that does change things somewhat. I'm not sure why it would be useful for a future version of Django to advertise support for a PostgreSQL version that the PostgreSQL project is itself intending to de-support. That seems likely to cause disappointment, even though you are correct and it will pass tests. I am just the messenger in this, carrying goodwill between projects. -- 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.
