Skip site navigation (1) Skip section navigation (2)

Re: Advisory Lock BIGINT Values

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: "David E(dot) Wheeler" <david(at)justatheory(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: Advisory Lock BIGINT Values
Date: 2012-08-28 02:36:58
Message-ID: 20120828023658.GG6786@momjian.us (view raw or flat)
Thread:
Lists: pgsql-hackers
On Fri, Mar  9, 2012 at 04:36:08PM -0800, David E. Wheeler wrote:
> Hackers,
> 
> The documentation for pg_locks says that, for BIGINT advisory locks:
> 
> > A bigint key is displayed with its high-order half in the classid column, its low-order half in the objid column
> 
> I was in need of knowing what the bigint is that is waiting on a lock, and Andrew Dunstan was kind enough to help me out with that. Since other folks might also need it, here’s a doc patch.
> 
> diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml
> new file mode 100644
> index 9564e01..de1c266
> *** a/doc/src/sgml/catalogs.sgml
> --- b/doc/src/sgml/catalogs.sgml
> ***************
> *** 7313,7319 ****
>      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
>      <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,
> --- 7313,7322 ----
>      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. 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
> !    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,

Thanks, applied.

-- 
  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +


In response to

Responses

pgsql-hackers by date

Next:From: Greg SmithDate: 2012-08-28 03:13:00
Subject: Re: Timing overhead and Linux clock sources
Previous:From: Bruce MomjianDate: 2012-08-28 02:21:27
Subject: Re: Incorrect behaviour when using a GiST index on points

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group