Date: Sat, 29 Jan 2022 19:43:27 -0800
From: Noah Misch <noah@leadboat.com>
To: Maxim Boguk <maxim.boguk@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>, Peter Geoghegan <pg@bowt.ie>,
	PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #17386: btree index corruption after reindex concurrently on
 write heavy table
Message-ID: <20220130034327.GA2619743@rfd.leadboat.com>
References: <17386-2227568627fb44ce@postgresql.org>
 <CAK-MWwQ7fboHz_s8aTn08i0W2aNH6QoELeWwmH-y80tOfsdDBQ@mail.gmail.com>
 <20220129023418.GA2452893@rfd.leadboat.com>
 <CAH2-WzkH8zHOS2X49jmc67_G5TXM8kNSh285nHKpmpf+qa8Rrg@mail.gmail.com>
 <YfTT7BBonfQYLPdX@paquier.xyz>
 <CAK-MWwReitx16bDQjT+ffAFwkQ_+2hdM+hwMvkRmaM835UxVrQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <CAK-MWwReitx16bDQjT+ffAFwkQ_+2hdM+hwMvkRmaM835UxVrQ@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: 
 <https://www.postgresql.org/message-id/20220130034327.GA2619743%40rfd.leadboat.com>
Precedence: bulk

On Sat, Jan 29, 2022 at 05:23:49PM +0200, Maxim Boguk wrote:
> On Sat, Jan 29, 2022 at 7:43 AM Michael Paquier <michael@paquier.xyz> wrote:
> > 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?
> 
> I don't remember such problems during the last year on v13 with the same
> workload and the same periodic reindex.

Got it.  A low-effort strategy would be to wait for v14.2 to release on
2022-02-10.  If the problem started with a v13.X -> v14.1 upgrade and ceases
in v14.2, then commit 18b87b20 likely was the fix.