From bf849af7f347ebcd394d6d789f557e75ead2f5ee Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Mon, 27 Aug 2012 22:36:37 -0400 Subject: [PATCH] Document how to create advisory lock "bigint" values in SQL. David E. Wheeler --- doc/src/sgml/catalogs.sgml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml index b100a426e4..bf568f1811 100644 --- a/doc/src/sgml/catalogs.sgml +++ b/doc/src/sgml/catalogs.sgml @@ -7412,7 +7412,10 @@ A bigint key is displayed with its high-order half in the classid column, its low-order half in the objid column, and objsubid equal - to 1. Integer keys are displayed with the first key in the + to 1. The original bigint value can be reassembled with the + expression (classid::int::bit(64) << 32 | + objid::int::bit(64))::bigint. Integer keys are displayed with the + first key in the classid column, the second key in the objid column, and objsubid equal to 2. The actual meaning of the keys is up to the user. Advisory locks are local to each database, -- 2.40.0