Date: Wed, 25 May 2022 23:17:33 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Peter Geoghegan <pg@bowt.ie>
Cc: Robert Haas <robertmhaas@gmail.com>,
	Alvaro Herrera <alvherre@alvh.no-ip.org>,
	Andres Freund <andres@anarazel.de>,
	Andrey Borodin <x4mmm@yandex-team.ru>,
	Michael Paquier <michael@paquier.xyz>,
	=?utf-8?B?0J/QtdGC0YrRgCDQodC70LDQstC+0LI=?= <pet.slavov@gmail.com>,
	PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #17485: Records missing from Primary Key index when doing
 REINDEX INDEX CONCURRENTLY
Message-ID: <Yo7xTUr3eNgxuBq4@momjian.us>
References: 
 <CA+TgmoYP7BnHXTEoJRUnOuie2J05Qo8ti5mnE2u-1c4Hk+8zJw@mail.gmail.com>
 <202205251643.2py5jjpaw7wy@alvherre.pgsql>
 <CA+TgmobNBHAObYS1yeX6C+Ph3ccborF86t9XFERdvtmmu-5DMg@mail.gmail.com>
 <CAH2-Wz=cDCzrfwm8YYF4vd8oMNJtVRh+_BbCqhCrKzX1NgXzQw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <CAH2-Wz=cDCzrfwm8YYF4vd8oMNJtVRh+_BbCqhCrKzX1NgXzQw@mail.gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/Yo7xTUr3eNgxuBq4%40momjian.us>
Precedence: bulk

On Wed, May 25, 2022 at 10:32:43AM -0700, Peter Geoghegan wrote:
> 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?

No, we are unlikely to wait until August.

What do we currently know?

*  Caused by CREATE/REINDEX CONCURRENTLY
*  No way to detect which indexes were created concurrently
*  amcheck will be required to find corrupt indexes (options?)
*  Heap is fine, only index is corrupt
*  Bug since PG 14
*  Not known why reports are only appearing now
*  Feature will likely need to be removed rather than fixed

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Indecision is a decision.  Inaction is an action.  Mark Batterson