Postgres Pro
Downloads
Home   >   mailing lists

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

From Noah Misch
Subject Re: BUG #17386: btree index corruption after reindex concurrently on write heavy table
Date
Msg-id 20220129023418.GA2452893@rfd.leadboat.com
Whole thread Raw
In response to Re: BUG #17386: btree index corruption after reindex concurrently on write heavy table  (Maxim Boguk <maxim.boguk@gmail.com>)
Responses Re: BUG #17386: btree index corruption after reindex concurrently on write heavy table  (Peter Geoghegan <pg@bowt.ie>)
Re: BUG #17386: btree index corruption after reindex concurrently on write heavy table  (Andres Freund <andres@anarazel.de>)
List pgsql-bugs
Tree view 
On Fri, Jan 28, 2022 at 04:17:28PM +0200, Maxim Boguk wrote:
> On Fri, Jan 28, 2022 at 3:42 PM PG Bug reporting form <noreply@postgresql.org> wrote:
> > PostgreSQL version: 14.1

> Seems something broken in combination of HOT update and REINDEX
> CONCURRENTLY.

Agreed.  Can you create a self-contained test case, perhaps by adapting
contrib/amcheck/t/002_cic.pl?  If this bug is like the ones fixed between 14.0
and 14.1, the base backup and WAL won't help us, unfortunately.  The transient
states are what matter.  I did try modifying the test to have elements of your
scenario, including HOT updates, KEY SHARE locks, and frozen tuples.  That
didn't reproduce the bug.  I'm attaching what I tried.
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: Peter Geoghegan
Date:
Subject: Re: BUG #17386: btree index corruption after reindex concurrently on write heavy table