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
Дата
Msg-id 20211109063119.ukcvdk7uvz7ks3pa@alap3.anarazel.de
обсуждение исходный текст
Ответ на Re: BUG #17268: Possible corruption in toast index after reindex index concurrently  (Noah Misch <noah@leadboat.com>)
Ответы Re: BUG #17268: Possible corruption in toast index after reindex index concurrently  (Noah Misch <noah@leadboat.com>)
Список pgsql-bugs
Дерево обсуждения 
Hi,

On 2021-11-08 21:46:25 -0800, Noah Misch wrote:
> Doing both sounds harmless.  Regarding REINDEX CONCURRENTLY on a system
> catalog, I bet that can still reach bugs even if we do both, considering this:

Normal catalog aren't REINDEX CONCURRENTLY. It's just toast tables that are
kind of system-y, but also kind of not, that can be reindexed concurrently. Or
at least I think it's just toast indexes?

Greetings,

Andres Freund

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

Предыдущее
От: Noah Misch
Дата:
Сообщение: 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