agora inbox for pgsql-bugs@postgresql.org
help / color / mirror / Atom feedFrom: Álvaro Herrera <alvherre@kurilemu.de>
To: Zsolt Parragi <zsolt.parragi@percona.com>
Cc: Christophe Pettus <xof@thebuild.com>
Cc: pgsql-hackers@lists.postgresql.org, Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Subject: Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes
Date: Thu, 10 Sep 2026 11:24:55 +0200
Message-ID: <aqJ0Qt-3teW-BhSN@alvherre.pgsql> (raw)
In-Reply-To: <ap-3KAqj28ED0TeA@alvherre.pgsql>
On 2026-Sep-08, Álvaro Herrera wrote:
> Yes, but I think the question is in which direction should we fix said
> bug. My preference is to go for Kyotaro's suggestion: have both REPACK
> and REPACK (CONCURRENTLY) raise an error with an invalid index, asking
> the user to drop it.
>
> Would anybody oppose that?
Concretely, something like this. (Hmm, I guess this should be noted in
repack.sgml as well.)
I don't want to touch the behavior of REINDEX, CLUSTER or VACUUM FULL in
pg19 at this stage, much less within the context of an "open item"; we
can discuss that for pg20 afterwards.
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"Uno puede defenderse de los ataques; contra los elogios se esta indefenso"
Attachments:
[text/x-diff] 0001-Fail-REPACK-in-presence-of-isready-indvalid-indexes.patch (0B, ../aqJ0Qt-3teW-BhSN@alvherre.pgsql/2-0001-Fail-REPACK-in-presence-of-isready-indvalid-indexes.patch)
download
view thread (16+ messages)
Message-ID: <aqJ0Qt-3teW-BhSN@alvherre.pgsql>
Permalink: ../aqJ0Qt-3teW-BhSN@alvherre.pgsql/
Also on: postgresql.org/message-id/aqJ0Qt-3teW-BhSN@alvherre.pgsql
reply
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@kurilemu.de, zsolt.parragi@percona.com, xof@thebuild.com, horikyota.ntt@gmail.com
Subject: Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes
In-Reply-To: <aqJ0Qt-3teW-BhSN@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 agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox