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

From Tom Lane
Subject Re: Need help understanding pg_locks
Date
Msg-id 6319.1310574694@sss.pgh.pa.us
Whole thread Raw
In response to Re: Need help understanding pg_locks  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Need help understanding pg_locks
List pgsql-hackers
Bruce Momjian <bruce@momjian.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.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "David E. Wheeler"
Date:
Subject: Re: Full GUID support
Next
From: Heikki Linnakangas
Date:
Subject: Re: Small patch for GiST: move childoffnum to child