Skip to content

Commit bf849af

Browse files
committed
Document how to create advisory lock "bigint" values in SQL.
David E. Wheeler
1 parent 7417a8e commit bf849af

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

doc/src/sgml/catalogs.sgml

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7412,7 +7412,10 @@
74127412
A <type>bigint</type> key is displayed with its
74137413
high-order half in the <structfield>classid</> column, its low-order half
74147414
in the <structfield>objid</> column, and <structfield>objsubid</> equal
7415-
to 1. Integer keys are displayed with the first key in the
7415+
to 1. The original <type>bigint</type> value can be reassembled with the
7416+
expression <literal>(classid::int::bit(64) &lt;&lt; 32 |
7417+
objid::int::bit(64))::bigint</literal>. Integer keys are displayed with the
7418+
first key in the
74167419
<structfield>classid</> column, the second key in the <structfield>objid</>
74177420
column, and <structfield>objsubid</> equal to 2. The actual meaning of
74187421
the keys is up to the user. Advisory locks are local to each database,

0 commit comments

Comments
 (0)
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy