Refer to PostgreSQL 9.0 documentation.

doc/src/advanced.rst

@@ -123,7 +123,7 @@ geometric type:
 
 
 .. |point| replace:: :sql:`point`
-.. _point: http://www.postgresql.org/docs/8.4/static/datatype-geometric.html#DATATYPE-GEOMETRIC
+.. _point: http://www.postgresql.org/docs/9.0/static/datatype-geometric.html#DATATYPE-GEOMETRIC
 
 The above function call results in the SQL command::
 
@@ -223,9 +223,9 @@ documentation), you should keep the connection in :ref:`autocommit
 manner.
 
 .. |LISTEN| replace:: :sql:`LISTEN`
-.. _LISTEN: http://www.postgresql.org/docs/8.4/static/sql-listen.html
+.. _LISTEN: http://www.postgresql.org/docs/9.0/static/sql-listen.html
 .. |NOTIFY| replace:: :sql:`NOTIFY`
-.. _NOTIFY: http://www.postgresql.org/docs/8.4/static/sql-notify.html
+.. _NOTIFY: http://www.postgresql.org/docs/9.0/static/sql-notify.html
 
 Notification are received after every query execution. If the user is interested
 in receiving notification but not in performing any query, the
@@ -327,7 +327,7 @@ completely non-blocking connection attempt: see the libpq documentation for
 |PQconnectStart|_.
 
 .. |PQconnectStart| replace:: `!PQconnectStart()`
-.. _PQconnectStart: http://www.postgresql.org/docs/8.4/static/libpq-connect.html#LIBPQ-PQCONNECTSTART
+.. _PQconnectStart: http://www.postgresql.org/docs/9.0/static/libpq-connect.html#LIBPQ-PQCONNECTSTART
 
 The same loop should be also used to perform nonblocking queries: after
 sending a query via `~cursor.execute()` or `~cursor.callproc()`, call
@@ -429,7 +429,7 @@ callback (using `!select()` to block) is provided as
 .. _Eventlet: http://eventlet.net/
 .. _gevent: http://www.gevent.org/
 .. _SQLAlchemy: http://www.sqlalchemy.org/
-.. __: http://www.postgresql.org/docs/8.4/static/libpq-async.html
+.. __: http://www.postgresql.org/docs/9.0/static/libpq-async.html
 
 .. warning::
     :ref:`COPY commands <copy>` are currently not supported when a wait callback

doc/src/connection.rst

@@ -103,10 +103,10 @@ The ``connection`` class
         session to the default values.
 
         .. |RESET| replace:: :sql:`RESET`
-        .. _RESET: http://www.postgresql.org/docs/8.4/static/sql-reset.html
+        .. _RESET: http://www.postgresql.org/docs/9.0/static/sql-reset.html
 
         .. |SET SESSION AUTHORIZATION| replace:: :sql:`SET SESSION AUTHORIZATION`
-        .. __: http://www.postgresql.org/docs/8.4/static/sql-set-session-authorization.html
+        .. __: http://www.postgresql.org/docs/9.0/static/sql-set-session-authorization.html
 
         .. versionadded:: 2.0.12
 
@@ -154,7 +154,7 @@ The ``connection`` class
         is the encoding defined by the database. It should be one of the
         `characters set supported by PostgreSQL`__
 
-        .. __: http://www.postgresql.org/docs/8.4/static/multibyte.html
+        .. __: http://www.postgresql.org/docs/9.0/static/multibyte.html
 
 
     .. index::
@@ -180,7 +180,7 @@ The ``connection`` class
         configuration parameters`__ such as ``log_statement``,
         ``client_min_messages``, ``log_min_duration_statement`` etc.
         
-        .. __: http://www.postgresql.org/docs/8.4/static/runtime-config-logging.html
+        .. __: http://www.postgresql.org/docs/9.0/static/runtime-config-logging.html
 
 
     .. attribute:: notifies
@@ -207,7 +207,7 @@ The ``connection`` class
 
         .. seealso:: libpq docs for `PQbackendPID()`__ for details.
 
-            .. __: http://www.postgresql.org/docs/8.4/static/libpq-status.html#LIBPQ-PQBACKENDPID
+            .. __: http://www.postgresql.org/docs/9.0/static/libpq-status.html#LIBPQ-PQBACKENDPID
 
         .. versionadded:: 2.0.8
 
@@ -228,7 +228,7 @@ The ``connection`` class
 
         .. seealso:: libpq docs for `PQparameterStatus()`__ for details.
 
-            .. __: http://www.postgresql.org/docs/8.4/static/libpq-status.html#LIBPQ-PQPARAMETERSTATUS
+            .. __: http://www.postgresql.org/docs/9.0/static/libpq-status.html#LIBPQ-PQPARAMETERSTATUS
 
         .. versionadded:: 2.0.12
 
@@ -245,7 +245,7 @@ The ``connection`` class
 
         .. seealso:: libpq docs for `PQtransactionStatus()`__ for details.
 
-            .. __: http://www.postgresql.org/docs/8.4/static/libpq-status.html#LIBPQ-PQTRANSACTIONSTATUS
+            .. __: http://www.postgresql.org/docs/9.0/static/libpq-status.html#LIBPQ-PQTRANSACTIONSTATUS
 
 
     .. index::
@@ -258,7 +258,7 @@ The ``connection`` class
 
         .. seealso:: libpq docs for `PQprotocolVersion()`__ for details.
 
-            .. __: http://www.postgresql.org/docs/8.4/static/libpq-status.html#LIBPQ-PQPROTOCOLVERSION
+            .. __: http://www.postgresql.org/docs/9.0/static/libpq-status.html#LIBPQ-PQPROTOCOLVERSION
 
         .. versionadded:: 2.0.12
 
@@ -276,7 +276,7 @@ The ``connection`` class
         
         .. seealso:: libpq docs for `PQserverVersion()`__ for details.
 
-            .. __: http://www.postgresql.org/docs/8.4/static/libpq-status.html#LIBPQ-PQSERVERVERSION
+            .. __: http://www.postgresql.org/docs/9.0/static/libpq-status.html#LIBPQ-PQSERVERVERSION
 
         .. versionadded:: 2.0.12
 
@@ -311,7 +311,7 @@ The ``connection`` class
         :rtype: `~psycopg2.extensions.lobject`
 
         .. |lo_import| replace:: `!lo_import()`
-        .. _lo_import: http://www.postgresql.org/docs/8.4/static/lo-interfaces.html#LO-IMPORT
+        .. _lo_import: http://www.postgresql.org/docs/9.0/static/lo-interfaces.html#LO-IMPORT
 
         .. versionadded:: 2.0.8
 

doc/src/cursor.rst

@@ -332,10 +332,10 @@ The ``cursor`` class
         flexibility.
 
         .. |CREATE-TABLE| replace:: :sql:`CREATE TABLE`
-        .. __: http://www.postgresql.org/docs/8.4/static/sql-createtable.html
+        .. __: http://www.postgresql.org/docs/9.0/static/sql-createtable.html
 
         .. |INSERT-RETURNING| replace:: :sql:`INSERT ... RETURNING`
-        .. __: http://www.postgresql.org/docs/8.4/static/sql-insert.html
+        .. __: http://www.postgresql.org/docs/9.0/static/sql-insert.html
 
 
     .. method:: nextset()
@@ -462,7 +462,7 @@ The ``cursor`` class
             ...
 
         .. |COPY| replace:: :sql:`COPY`
-        .. __: http://www.postgresql.org/docs/8.4/static/sql-copy.html
+        .. __: http://www.postgresql.org/docs/9.0/static/sql-copy.html
 
         .. versionadded:: 2.0.6
 

doc/src/errorcodes.rst

@@ -39,7 +39,7 @@ From PostgreSQL documentation:
 
 .. seealso:: `PostgreSQL Error Codes table`__
 
-    .. __: http://www.postgresql.org/docs/8.4/static/errcodes-appendix.html#ERRCODES-TABLE
+    .. __: http://www.postgresql.org/docs/9.0/static/errcodes-appendix.html#ERRCODES-TABLE
 
 
 An example of the available constants defined in the module:

doc/src/extensions.rst

@@ -70,7 +70,7 @@ functionalities defined by the |DBAPI|_.
         The method uses the efficient |lo_export|_ libpq function.
         
         .. |lo_export| replace:: `!lo_export()`
-        .. _lo_export: http://www.postgresql.org/docs/8.4/static/lo-interfaces.html#LO-EXPORT
+        .. _lo_export: http://www.postgresql.org/docs/9.0/static/lo-interfaces.html#LO-EXPORT
 
     .. method:: seek(offset, whence=0)
 
@@ -91,7 +91,7 @@ functionalities defined by the |DBAPI|_.
         running these versions. It uses the |lo_truncate|_ libpq function.
 
         .. |lo_truncate| replace:: `!lo_truncate()`
-        .. _lo_truncate: http://www.postgresql.org/docs/8.4/static/lo-interfaces.html#LO-TRUNCATE
+        .. _lo_truncate: http://www.postgresql.org/docs/9.0/static/lo-interfaces.html#LO-TRUNCATE
 
     .. method:: close()
 
@@ -291,7 +291,7 @@ details.
     Used by Psycopg when adapting or casting unicode strings. See
     :ref:`unicode-handling`.
 
-    .. __: http://www.postgresql.org/docs/8.4/static/multibyte.html
+    .. __: http://www.postgresql.org/docs/9.0/static/multibyte.html
     .. __: http://docs.python.org/library/codecs.html#standard-encodings
 
 

doc/src/faq.rst

@@ -33,7 +33,7 @@ I receive the error *current transaction is aborted, commands ignored until end
     PostgreSQL supports nested transactions using the |SAVEPOINT|_ command).
 
     .. |SAVEPOINT| replace:: :sql:`SAVEPOINT`
-    .. _SAVEPOINT: http://www.postgresql.org/docs/8.4/static/sql-savepoint.html
+    .. _SAVEPOINT: http://www.postgresql.org/docs/9.0/static/sql-savepoint.html
 
 Why do i get the error *current transaction is aborted, commands ignored until end of transaction block* when I use `!multiprocessing` (or any other forking system) and not when use `!threading`?
     Psycopg's connections can't be shared across processes (but are thread

doc/src/index.rst

@@ -21,9 +21,9 @@ PostgreSQL arrays.
 .. _PostgreSQL: http://www.postgresql.org/
 .. _Python: http://www.python.org/
 .. _Zope: http://www.zope.org/
-.. _libpq: http://www.postgresql.org/docs/8.4/static/libpq.html
+.. _libpq: http://www.postgresql.org/docs/9.0/static/libpq.html
 .. |COPY-TO-FROM| replace:: :sql:`COPY TO/COPY FROM`
-.. __: http://www.postgresql.org/docs/8.4/static/sql-copy.html
+.. __: http://www.postgresql.org/docs/9.0/static/sql-copy.html
 
 
 .. rubric:: Contents

doc/src/module.rst

@@ -38,7 +38,7 @@ The module interface respects the standard defined in the |DBAPI|_.
     - `port` -- connection port number (defaults to 5432 if not provided)
     - `sslmode` -- `SSL TCP/IP negotiation`__ mode
 
-    .. __: http://www.postgresql.org/docs/8.4/static/libpq-ssl.html#LIBPQ-SSL-SSLMODE-STATEMENTS
+    .. __: http://www.postgresql.org/docs/9.0/static/libpq-ssl.html#LIBPQ-SSL-SSLMODE-STATEMENTS
 
     Using the *connection_factory* parameter a different class or
     connections factory can be specified. It should be a callable object

doc/src/usage.rst

@@ -313,7 +313,7 @@ defined on the database connection (the `PostgreSQL encoding`__, available in
 
     >>> cur.execute("INSERT INTO test (num, data) VALUES (%s,%s);", (74, u))
 
-.. __: http://www.postgresql.org/docs/8.4/static/multibyte.html
+.. __: http://www.postgresql.org/docs/9.0/static/multibyte.html
 .. __: http://docs.python.org/library/codecs.html#standard-encodings
 
 When reading data from the database, the strings returned are usually 8 bit
@@ -463,7 +463,7 @@ method and to read the data using `~cursor.fetchone()` and
 `~cursor.fetchmany()` methods.
 
 .. |DECLARE| replace:: :sql:`DECLARE`
-.. _DECLARE: http://www.postgresql.org/docs/8.4/static/sql-declare.html
+.. _DECLARE: http://www.postgresql.org/docs/9.0/static/sql-declare.html
 
 
 
@@ -510,7 +510,7 @@ Please refer to the documentation of the single methods for details and
 examples.
 
 .. |COPY| replace:: :sql:`COPY`
-.. __: http://www.postgresql.org/docs/8.4/static/sql-copy.html
+.. __: http://www.postgresql.org/docs/9.0/static/sql-copy.html
 
 
 
@@ -527,7 +527,7 @@ access to user data that is stored in a special large-object structure. They
 are useful with data values too large to be manipulated conveniently as a
 whole.
 
-.. __: http://www.postgresql.org/docs/8.4/static/largeobjects.html
+.. __: http://www.postgresql.org/docs/9.0/static/largeobjects.html
 
 Psycopg allows access to the large object using the
 `~psycopg2.extensions.lobject` class. Objects are generated using the
@@ -537,6 +537,6 @@ Psycopg large object support efficient import/export with file system files
 using the |lo_import|_ and |lo_export|_ libpq functions.
 
 .. |lo_import| replace:: `!lo_import()`
-.. _lo_import: http://www.postgresql.org/docs/8.4/static/lo-interfaces.html#LO-IMPORT
+.. _lo_import: http://www.postgresql.org/docs/9.0/static/lo-interfaces.html#LO-IMPORT
 .. |lo_export| replace:: `!lo_export()`
-.. _lo_export: http://www.postgresql.org/docs/8.4/static/lo-interfaces.html#LO-EXPORT
+.. _lo_export: http://www.postgresql.org/docs/9.0/static/lo-interfaces.html#LO-EXPORT