documentation about explicit locking - Mailing list pgsql-hackers

From Amit Langote
Subject documentation about explicit locking
Date
Msg-id e595ef72-e3aa-23f6-e89d-228872c95bc0@lab.ntt.co.jp
Whole thread Raw
Responses Re: documentation about explicit locking  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Hi.

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.

Thanks,
Amit



pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: why partition pruning doesn't work?
Next
From: "Ideriha, Takeshi"
Date:
Subject: RE: Global shared meta cache