Re: documentation about explicit locking

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: documentation about explicit locking
Дата
Msg-id CA+TgmoYLSf=OZ0oP7VseNde=0H_xT9d2W=1nD8im4LnX510hKw@mail.gmail.com
обсуждение исходный текст
Ответ на documentation about explicit locking  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Ответы Re: documentation about explicit locking  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Список pgsql-hackers
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.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: Global shared meta cache
Следующее
От: Andrey Borodin
Дата:
Сообщение: Re: Why B-Tree suffix truncation matters