Horton

Re: BUG #17485: Records missing from Primary Key index when doing REINDEX INDEX CONCURRENTLY

Peter Geoghegan <pg@bowt.ie>

View thread View on postgr.es
From: Peter Geoghegan <pg@bowt.ie>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>, Andres Freund <andres@anarazel.de>, Andrey Borodin <x4mmm@yandex-team.ru>, Michael Paquier <michael@paquier.xyz>, Петър Славов <pet.slavov@gmail.com>, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Date: 2022-05-25T17:32:43Z
Lists: pgsql-bugs 
On Wed, May 25, 2022 at 10:18 AM Robert Haas <robertmhaas@gmail.com> wrote:
> Right, I mean I'm not saying I *like* reverting, and I'm not disputing
> it's a good feature. Just that, if we have to choose between this
> feature and not having index corruption, we better not have index
> corruption.... and I'm not seeing any way that we can just tweak this
> and make it work.

Are we any closer to deciding on a timeline, in light of recent discussion?

I'm now convinced that an out-of-schedule release is probably the way
to go. My thinking is: are we really going to make users wait for
August 11th for a fix?

-- 
Peter Geoghegan

Commits

  1. Revert changes to CONCURRENTLY that "sped up" Xmin advance

  2. Fix possible HOT corruption when RECENTLY_DEAD changes to DEAD while pruning.