Re: [DOC] Document concurrent index builds waiting on each other

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: [DOC] Document concurrent index builds waiting on each other
Дата
Msg-id 20200930091010.GU1996@paquier.xyz
обсуждение исходный текст
Ответ на Re: [DOC] Document concurrent index builds waiting on each other  (James Coleman <jtc331@gmail.com>)
Ответы Re: [DOC] Document concurrent index builds waiting on each other  ("David G. Johnston" <david.g.johnston@gmail.com>)
Re: [DOC] Document concurrent index builds waiting on each other  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Список pgsql-hackers
On Tue, Sep 08, 2020 at 01:25:21PM -0400, James Coleman wrote:
> Álvaro's patch confused the current state of this thread, so I'm
> reattaching (rebased) v2 as v3.

+  <para>
+   <command>CREATE INDEX</command> (including the <literal>CONCURRENTLY</literal>
+   option) commands are included when <command>VACUUM</command> calculates what
+   dead tuples are safe to remove even on tables other than the one being indexed.
+  </para>
FWIW, this is true as well for REINDEX CONCURRENTLY because both use
the same code paths for index builds and validation, with basically
the same waiting phases.  But is CREATE INDEX the correct place for
that?  Wouldn't it be better to tell about such things on the VACUUM
doc?

0001 sounds fine to me.
--
Michael

Вложения

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

Предыдущее
От: Amit Kapila
Дата:
Сообщение: Re: [HACKERS] logical decoding of two-phase transactions
Следующее
От: Amit Kapila
Дата:
Сообщение: Re: Resetting spilled txn statistics in pg_stat_replication