Re: BUG #17268: Possible corruption in toast index after reindex index concurrently

Поиск
Список
Период
Сортировка
От Noah Misch
Тема Re: BUG #17268: Possible corruption in toast index after reindex index concurrently
Дата
Msg-id 20211109035624.GA940092@rfd.leadboat.com
обсуждение исходный текст
Ответ на Re: BUG #17268: Possible corruption in toast index after reindex index concurrently  (Andres Freund <andres@anarazel.de>)
Ответы Re: BUG #17268: Possible corruption in toast index after reindex index concurrently  (Andres Freund <andres@anarazel.de>)
Список pgsql-bugs
Дерево обсуждения 
On Mon, Nov 08, 2021 at 12:36:41PM -0800, Andres Freund wrote:
> One possible way to fix this would be to make ReindexRelationConcurrently()
> acquire a lock on the underlying table when reindexing a toast table. Another
> to not release the lock in toast_save_datum().

The latter is more future-proof.  Does it have material disadvantages?

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

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: BUG #17268: Possible corruption in toast index after reindex index concurrently
Следующее
От: Andres Freund
Дата:
Сообщение: Re: BUG #17268: Possible corruption in toast index after reindex index concurrently