Re: documentation about explicit locking

Поиск
Список
Период
Сортировка
От Amit Langote
Тема Re: documentation about explicit locking
Дата
Msg-id 4f94dddd-47aa-62a9-a32f-626ae99be8b8@lab.ntt.co.jp
обсуждение исходный текст
Ответ на Re: documentation about explicit locking  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: documentation about explicit locking  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Список 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

Вложения

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

Предыдущее
От: Amit Langote
Дата:
Сообщение: Re: Global shared meta cache
Следующее
От: Thomas Munro
Дата:
Сообщение: Re: hot_standby_feedback vs excludeVacuum and snapshots