From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Christophe Pettus <xof@thebuild.com>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: Peter Geoghegan <pg@bowt.ie>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Andres Freund <andres@anarazel.de>
Cc: Andrey Borodin <x4mmm@yandex-team.ru>
Cc: Петър Славов <pet.slavov@gmail.com>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #17485: Records missing from Primary Key index when doing REINDEX INDEX CONCURRENTLY
Date: Tue, 31 May 2022 16:43:00 +0200
Message-ID: <202205311443.5xshc44kp7ll@alvherre.pgsql> (raw)
In-Reply-To: <BB3FB2D1-9796-442B-AF11-08DFD0BF0F57@thebuild.com>
On 2022-May-26, Christophe Pettus wrote:
> Unless we are 100% sure that amcheck will never return a false
> negative in this situation, we may have to recommend reindexing
> everything.
I am not aware of any reason why amcheck would return a false negative.
Is there any evidence behind this assertion?
If there is none, the recommendation should be to use amcheck on all
btree indexes and reindex those that have the problem; and reindex all
indexes of other AMs that could have been reindexed or created
concurrently in 14beta1 or later (implying: an index that was created in
13 and pg_upgraded but not touched afterwards is not at risk).
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: alvherre@alvh.no-ip.org, xof@thebuild.com, bruce@momjian.us, michael@paquier.xyz, pg@bowt.ie, robertmhaas@gmail.com, andres@anarazel.de, x4mmm@yandex-team.ru, pet.slavov@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17485: Records missing from Primary Key index when doing REINDEX INDEX CONCURRENTLY
In-Reply-To: <202205311443.5xshc44kp7ll@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox