From: Bruce Momjian <bruce@momjian.us>
Date: Tue, 28 Aug 2012 16:17:11 +0000 (-0400)
Subject: Update doc mention of how to compute bigint advisory lock value, per Tom
X-Git-Tag: REL9_3_BETA1~1010
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=5ea6c9d79882815d4cc1c3c302f415eb637466f2;p=thirdparty%2Fpostgresql.git

Update doc mention of how to compute bigint advisory lock value, per Tom
Lane's correction.
---

diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml
index bf568f18113..3bcd82cbdd3 100644
--- a/doc/src/sgml/catalogs.sgml
+++ b/doc/src/sgml/catalogs.sgml
@@ -7413,8 +7413,8 @@
    high-order half in the <structfield>classid</> column, its low-order half
    in the <structfield>objid</> column, and <structfield>objsubid</> equal
    to 1. The original <type>bigint</type> value can be reassembled with the
-   expression <literal>(classid::int::bit(64) &lt;&lt; 32 |
-   objid::int::bit(64))::bigint</literal>. Integer keys are displayed with the
+   expression <literal>(classid::bigint &lt;&lt; 32) |
+   objid::bigint</literal>. Integer keys are displayed with the
    first key in the
    <structfield>classid</> column, the second key in the <structfield>objid</>
    column, and <structfield>objsubid</> equal to 2.  The actual meaning of