Horton

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

Noah Misch <noah@leadboat.com>

View thread View on postgr.es
From: Noah Misch <noah@leadboat.com>
To: Andres Freund <andres@anarazel.de>
Cc: Michael Paquier <michael@paquier.xyz>, Alexey Ermakov <alexey.ermakov@dataegret.com>, Robert Haas <robertmhaas@gmail.com>, Maxim Boguk <maxim.boguk@gmail.com>, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>, Peter Geoghegan <pg@bowt.ie>
Date: 2021-11-09T06:42:17Z
Lists: 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.

Commits

  1. Fix corruption of toast indexes with REINDEX CONCURRENTLY