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

Поиск
Список
Период
Сортировка
От James Coleman
Тема Re: [DOC] Document concurrent index builds waiting on each other
Дата
Msg-id CAAaqYe9-PCuvq=0C39E5UqLHpVShc8tL5nBrB_sXJDgUCVDe=A@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [DOC] Document concurrent index builds waiting on each other  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Ответы Re: [DOC] Document concurrent index builds waiting on each other  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Список pgsql-hackers
On Wed, Jan 13, 2021 at 4:05 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
>
> On 2021-Jan-13, James Coleman wrote:
>
> > On Wed, Jan 13, 2021 at 12:33 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
>
> > > This is true.  So I propose
> > >
> > >     Like any long-running transaction, <command>REINDEX</command> can
> > >     affect which tuples can be removed by concurrent <command>VACUUM</command>
> > >     on any table.
> >
> > That sounds good to me.
>
> Great, pushed with one more wording tweak: "REINDEX on any table can
> affect ... on any other table".  To pg12 and up.

Looks like what got committed is "REINDEX on a table" not "on any",
but I'm not sure that matters too much.

James



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

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: [DOC] Document concurrent index builds waiting on each other
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: [DOC] Document concurrent index builds waiting on each other