Re: Need help understanding pg_locks

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Florian Pflug <fgp(at)phlo(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Need help understanding pg_locks
Date: 2011-07-13 18:45:51
Message-ID: 4E1DE7DF.4010605@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 07/13/2011 12:31 PM, Tom Lane wrote:
> Bruce Momjian<bruce(at)momjian(dot)us> writes:
>> Tom Lane wrote:
>>> I think you misunderstood the suggestion. This is not an improvement,
>>> it's just more confusion.
>> Well, I thought the "lock on" wording helped avoid the confusion but
>> obviously I didn't understand more than that. We did have similar
>> confusion when we clarified the locking C code. For me, "object" was
>> the stumbler. Do you have any suggested wording? Everyone seems to
>> agree it needs improvement.
> Well, first, "lock object" is completely useless, it does not convey
> more than "lock" does; and second, you've added confusion because the
> very same sentences also use "object" to refer to the thing being
> locked.
>

Maybe "lock" for the lock itself and "lock target" for the thing locked,
or some such, would work.

I agree that "object" on its own is not a terribly helpful term. It's
too often shorthand for "whatever-it-is".

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2011-07-13 18:56:47 Re: Small patch for GiST: move childoffnum to child
Previous Message Bruce Momjian 2011-07-13 18:43:08 Re: [BUGS] extract(epoch from infinity) is not 0