From d16ebde58275d848968e758ec643efc8ce64c8fa Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Mon, 28 Nov 2011 13:52:09 -0500
Subject: [PATCH] Remove erroneous claim about use of pg_locks.objid for
 advisory locks.

The correct information appears in the text, so just remove the statement
in the table, where it did not fit nicely anyway.  (Curiously, the correct
info has been there much longer than the erroneous table entry.)
Resolves problem noted by Daniele Varrazzo.

In HEAD and 9.1, also do a bit of wordsmithing on other text on the page.
---
 doc/src/sgml/catalogs.sgml | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml
index a2869c917e..2f4db2c013 100644
--- a/doc/src/sgml/catalogs.sgml
+++ b/doc/src/sgml/catalogs.sgml
@@ -6302,10 +6302,7 @@
       <entry>any OID column</entry>
       <entry>
        OID of the object within its system catalog, or null if the
-       object is not a general database object.
-       For advisory locks it is used to distinguish the two key
-       spaces (<literal>1</> for an int8 key, <literal>2</> for two
-       int4 keys).
+       object is not a general database object
       </entry>
      </row>
      <row>