diff options
| author | Bruce Momjian <bruce@momjian.us> | 2012-08-27 22:36:37 -0400 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2012-08-27 22:36:48 -0400 |
| commit | bf849af7f347ebcd394d6d789f557e75ead2f5ee (patch) | |
| tree | 55400dc143000ff186a258bbb48dd4246284c1af | |
| parent | 7417a8e3dd14886887447053a5ccbd4f9501ba61 (diff) | |
| download | postgresql-bf849af7f347ebcd394d6d789f557e75ead2f5ee.tar.gz postgresql-bf849af7f347ebcd394d6d789f557e75ead2f5ee.zip | |
Document how to create advisory lock "bigint" values in SQL.
David E. Wheeler
| -rw-r--r-- | doc/src/sgml/catalogs.sgml | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml index b100a426e48..bf568f18113 100644 --- a/doc/src/sgml/catalogs.sgml +++ b/doc/src/sgml/catalogs.sgml @@ -7412,7 +7412,10 @@ A <type>bigint</type> key is displayed with its high-order half in the <structfield>classid</> column, its low-order half in the <structfield>objid</> column, and <structfield>objsubid</> equal - to 1. Integer keys are displayed with the first key in the + to 1. The original <type>bigint</type> value can be reassembled with the + expression <literal>(classid::int::bit(64) << 32 | + objid::int::bit(64))::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 the keys is up to the user. Advisory locks are local to each database, |