Postgres Pro
Downloads
Home   >   mailing lists

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 20211109035624.GA940092@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
Tree view 
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 by date:

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