Re: Need help understanding pg_locks - Mailing list pgsql-hackers

From Florian Pflug
Subject Re: Need help understanding pg_locks
Date
Msg-id E2DE4283-8102-4959-81D7-F1F3B0031A66@phlo.org
Whole thread Raw
In response to Re: Need help understanding pg_locks  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Need help understanding pg_locks  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Jul11, 2011, at 05:47 , Bruce Momjian wrote:
> Thank you.  I think my confusion is that virtualtransaction is the lock
> holder/waiter, and the other two are actual locks.  The attached doc
> patch clarifies that.  I had actually realized this a few weeks ago and
> forgot, meaning this is pretty confusing.

For consistency, I guess it should say "lock object" instead of simply
"object" the description of all the columns up to (and including)
"objsubid", not only those of "virtualxid" and "transactionid".

I'd also slightly prefer "locked object" over "lock object", because
the lock itself probably isn't a standalone entity in the mind of
most users. And for people familiar with our locking infrastructure,
the actually correct term would be "lock tag" I believe.

In any case, +1 for improving the description there.

best regards,
Florian Pflug



pgsql-hackers by date:

Previous
From: Florian Pflug
Date:
Subject: Re: [GENERAL] Creating temp tables inside read only transactions
Next
From: Shigeru Hanada
Date:
Subject: Re: per-column generic option