Re: BUG #17268: Possible corruption in toast index after reindex index concurrently - Mailing list pgsql-bugs

From Andres Freund
Subject Re: BUG #17268: Possible corruption in toast index after reindex index concurrently
Date
Msg-id 20211109063119.ukcvdk7uvz7ks3pa@alap3.anarazel.de
Whole thread Raw
In response to Re: BUG #17268: Possible corruption in toast index after reindex index concurrently  (Noah Misch <noah@leadboat.com>)
Responses Re: BUG #17268: Possible corruption in toast index after reindex index concurrently
List 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 by date:

Previous
From: Noah Misch
Date:
Subject: Re: BUG #17268: Possible corruption in toast index after reindex index concurrently
Next
From: Noah Misch
Date:
Subject: Re: BUG #17268: Possible corruption in toast index after reindex index concurrently