From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Andres Freund <andres@anarazel.de>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: Andrey Borodin <x4mmm@yandex-team.ru>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Peter Geoghegan <pg@bowt.ie>
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 19:35:58 +0200
Message-ID: <202205311735.6ee52cp3igf7@alvherre.pgsql> (raw)
In-Reply-To: <20220530205125.uyxvvolr4xfdykwt@alap3.anarazel.de>
On 2022-May-30, Andres Freund wrote:
> On 2022-05-30 22:40:39 +0200, Alvaro Herrera wrote:
> > c98763bf51bf Avoid spurious waits in concurrent indexing
> > f9900df5f949 Avoid spurious wait in concurrent reindex
> > d9d076222f5b VACUUM: ignore indexing operations with CONCURRENTLY
>
> That looks right, yes.
Sorry, after going through these commits again, this is a
misunderstanding on my part. The first two commits need not be
reverted; only the third one does, which is the one that changes the way
the system-wide Xmin is determined (the commit message says it affects
VACUUM, but naturally it affects HOT pruning as well.)
The point of the first two changes is to remove snapshot waits in CIC
and RC. Before those commits, each CIC would wait for all other CICs
and RCs in the system. AFAICS this is unrelated to the HOT-pruning bug.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"Para tener más hay que desear menos"
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, andres@anarazel.de, michael@paquier.xyz, x4mmm@yandex-team.ru, robertmhaas@gmail.com, pg@bowt.ie, 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: <202205311735.6ee52cp3igf7@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