pgsql: Remove erroneous claim about use of pg_locks.objid for advisory

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Remove erroneous claim about use of pg_locks.objid for advisory
Date: 2011-11-28 18:52:45
Message-ID: E1RV6Jp-0005cj-8c@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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.

Branch
------
REL9_1_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/8ab9df0db196b6e1afa75838394eb27e9955e80e

Modified Files
--------------
doc/src/sgml/catalogs.sgml | 48 ++++++++++++++++++++++---------------------
1 files changed, 25 insertions(+), 23 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Dave Page 2011-11-28 18:53:49 stackbuilder - wizard: Don't try to open the registry file in read/write
Previous Message Tom Lane 2011-11-28 17:51:58 pgsql: Fix some bogosities in pg_dump's foreign-table support.