Re: BUG #17386: btree index corruption after reindex concurrently on write heavy table - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #17386: btree index corruption after reindex concurrently on write heavy table
Date
Msg-id YfTT7BBonfQYLPdX@paquier.xyz
Whole thread Raw
In response to Re: BUG #17386: btree index corruption after reindex concurrently on write heavy table  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: BUG #17386: btree index corruption after reindex concurrently on write heavy table
List pgsql-bugs
On Fri, Jan 28, 2022 at 07:00:31PM -0800, Peter Geoghegan wrote:
> If I had to guess, then I'd guess that this has something to do with
> orphaned HOT chains, like those we saw in the bug report that led to
> bugfix commit 18b87b20 (which is in 14.2 but not 14.1). I could easily
> be wrong about that, so take it with a grain of salt. I find it a
> little suspicious that we're hearing about a REINDEX CONCURRENTLY
> problem in Postgres 14, which is much less mature than Postgres 12
> (where REINDEX CONCURRENTLY first appeared).

Possible, but hard to say without an actual proof.  Maxim, if the
problem is reproducible easily on your end, could you give a try to v12
and v13 and see if it happens as well there?
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #17387: Working in PG13 but not in PGH14: array_agg(RECORD)
Next
From: Maxim Boguk
Date:
Subject: Re: BUG #17386: btree index corruption after reindex concurrently on write heavy table