Fixed #19968 -- Dropped support for PostgreSQL < 8.4.

1 files changed, 3 insertions, 3 deletions

diff --git a/docs/ref/unicode.txt b/docs/ref/unicode.txt
index 92a446ff6b..bd5bdc96a9 100644
--- a/docs/ref/unicode.txt
+++ b/docs/ref/unicode.txt
@@ -20,14 +20,14 @@ able to store certain characters in the database, and information will be lost.
 * MySQL users, refer to the `MySQL manual`_ (section 9.1.3.2 for MySQL 5.1)
   for details on how to set or alter the database character set encoding.
 
-* PostgreSQL users, refer to the `PostgreSQL manual`_ (section 21.2.2 in
-  PostgreSQL 8) for details on creating databases with the correct encoding.
+* PostgreSQL users, refer to the `PostgreSQL manual`_ (section 22.3.2 in
+  PostgreSQL 9) for details on creating databases with the correct encoding.
 
 * SQLite users, there is nothing you need to do. SQLite always uses UTF-8
   for internal encoding.
 
 .. _MySQL manual: http://dev.mysql.com/doc/refman/5.1/en/charset-database.html
-.. _PostgreSQL manual: http://www.postgresql.org/docs/8.2/static/multibyte.html#AEN24104
+.. _PostgreSQL manual: http://www.postgresql.org/docs/current/static/multibyte.html
 
 All of Django's database backends automatically convert Unicode strings into
 the appropriate encoding for talking to the database. They also automatically