Fixed #16255 -- Raised minimum PostgreSQL version supported to 8.2.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@16423 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Ramiro Morales 2011-06-16 20:05:25 +00:00
parent b2f5efc6ac
commit b870bf6b9a
4 changed files with 24 additions and 51 deletions

View file

@ -16,21 +16,9 @@ documentation or reference manuals.
PostgreSQL notes
================
.. versionchanged:: 1.3
.. versionchanged:: 1.4
Django supports PostgreSQL 8.0 and higher. If you want to use
:ref:`database-level autocommit <postgresql-autocommit-mode>`, a
minimum version of PostgreSQL 8.2 is required.
.. admonition:: Improvements in recent PostgreSQL versions
PostgreSQL 8.0 and 8.1 `will soon reach end-of-life`_; there have
also been a number of significant performance improvements added
in recent PostgreSQL versions. Although PostgreSQL 8.0 is the minimum
supported version, you would be well advised to use a more recent
version if at all possible.
.. _will soon reach end-of-life: http://wiki.postgresql.org/wiki/PostgreSQL_Release_Support_Policy
Django supports PostgreSQL 8.2 and higher.
PostgreSQL 8.2 to 8.2.4
-----------------------

View file

@ -376,3 +376,14 @@ Old styles of calling ``cache_page`` decorator
Some legacy ways of calling :func:`~django.views.decorators.cache.cache_page`
have been deprecated, please see the docs for the correct way to use this
decorator.
Support for PostgreSQL versions older than 8.2
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Django 1.3 dropped support for PostgreSQL versions older than 8.0 and the
relevant documents suggested to use a recent version because of performance
reasons but more importantly because end of the upstream support periods for
releases 8.0 and 8.1 was near (November 2010.)
Django 1.4 takes that policy further and sets 8.2 as the minimum PostgreSQL
version it officially supports.