Re: Required locks for ANALYZE

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Required locks for ANALYZE
Дата
Msg-id 6129.1566310344@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Required locks for ANALYZE  (PG Doc comments form <noreply@postgresql.org>)
Ответы RE: Required locks for ANALYZE
Список pgsql-docs
PG Doc comments form <noreply@postgresql.org> writes:
> Therefore, in my opinion, the below paragraph should be amended as below.

> * Before
> -----
> ANALYZE requires only a read lock on the target table, so it can run in
> parallel with other activity on the table.
> -----

> * After
> -----
> ANALYZE requires only a SHARE UPDATE EXCLUSIVE lock on the target table, so
> it can run in parallel with queries requiring ACCESS SHARE/ROW SHARE/ROW
> EXCLUSIVE locks such as SELECT, UPDATE, DELETE, INSERT on the table.
> -----

This does not really seem like an improvement.  The second formulation is
pedantically correct, but also unintelligible.

Maybe we could make it say "run in parallel with non-DDL activity" ?

            regards, tom lane



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

Предыдущее
От: PG Doc comments form
Дата:
Сообщение: Server Configuration: Replication documentation
Следующее
От: "Joshua D. Drake"
Дата:
Сообщение: Re: readability changes to postgres.sgml