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

From Noah Misch
Subject Re: BUG #17268: Possible corruption in toast index after reindex index concurrently
Date
Msg-id 20211109064217.GC940092@rfd.leadboat.com
Whole thread Raw
In response to Re: BUG #17268: Possible corruption in toast index after reindex index concurrently  (Andres Freund <andres@anarazel.de>)
Responses Re: BUG #17268: Possible corruption in toast index after reindex index concurrently
List pgsql-bugs
On Mon, Nov 08, 2021 at 10:31:19PM -0800, Andres Freund wrote:
> 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.

Oh, okay.



pgsql-bugs by date:

Previous
From: Andres Freund
Date:
Subject: Re: BUG #17268: Possible corruption in toast index after reindex index concurrently
Next
From: 菊池祐
Date:
Subject: Re: BUG #17269: Why is virtual memory usage of PostgreSQL growing constantly?