Re: documentation about explicit locking - Mailing list pgsql-hackers

From Amit Langote
Subject Re: documentation about explicit locking
Date
Msg-id 4f94dddd-47aa-62a9-a32f-626ae99be8b8@lab.ntt.co.jp
Whole thread Raw
In response to Re: documentation about explicit locking  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: documentation about explicit locking  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On 2018/07/05 23:02, Robert Haas wrote:
> On Wed, Jul 4, 2018 at 3:09 AM, Amit Langote
> <Langote_Amit_f8@lab.ntt.co.jp> wrote:
>> I wonder why we mention on the following page that CREATE COLLATION
>> requires SHARE ROW EXCLUSIVE lock
>>
>> https://www.postgresql.org/docs/devel/static/explicit-locking.html
>>
>> I know that's the lock taken on the pg_collation catalog, but do we need
>> to mention locks taken by a DDL command on the catalogs it affects?  All
>> other commands mentioned on the page require to specify the table name
>> that the lock will be taken on.
> 
> Yes, that looks odd.

OK, here is a patch.

I see that it was one of Peter E's commits that added that, so cc'd him.

Thanks,
Amit

Attachment

pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: Global shared meta cache
Next
From: Thomas Munro
Date:
Subject: Re: hot_standby_feedback vs excludeVacuum and snapshots