postgres.git / summary / log / commit / refs

commit    de9b2cb3f4346fb9ff5c90c61ff40b48b83cbafc
Author:   Tom Lane <tgl@sss.pgh.pa.us>
Date:     Mon Nov 28 18:52:15 2011 +0000
First released in: 9.2.0, 8.4.10, 9.0.6, 9.1.2

    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 18c21000aa8..6381d4e0446 100644
--- a/doc/src/sgml/catalogs.sgml
+++ b/doc/src/sgml/catalogs.sgml
@@ -5990,10 +5990,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>


[parent: 31e9743f1ab9]