agora inbox for pgsql-bugs@postgresql.org  

help / color / mirror / Atom feed

From: Álvaro Herrera <alvherre@kurilemu.de>
To: Zsolt Parragi <zsolt.parragi@percona.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes
Date: Mon, 27 Jul 2026 13:05:50 +0200
Message-ID: <amc6yk-z0XYg0SjF@alvherre.pgsql> (raw)
In-Reply-To: <CAN4CZFO5A3YE0Dd-bn7eKrB20pECO3=U0wKg1z2rO=DxgWJJHQ@mail.gmail.com>

Hello,

On 2026-Jul-21, Zsolt Parragi wrote:

> While testing REPACK, I noticed that REPACK (CONCURRENTLY) fails with
> invalid unique indexes, while the non-concurrent version handles them.

Thanks for testing!

> The attached patch mirrors this handling for CONCURRENTLY: constraints
> won't be enforced for invalid indexes.

Wouldn't it make more sense to just ignore invalid indexes and not build
anything at all for them?

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/

view thread (21+ messages)  latest in thread

Message-ID: <amc6yk-z0XYg0SjF@alvherre.pgsql>
Permalink:  ../amc6yk-z0XYg0SjF@alvherre.pgsql/
Also on:    postgresql.org/message-id/amc6yk-z0XYg0SjF@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, pgsql-bugs@lists.postgresql.org
  Subject: Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes
  In-Reply-To: <amc6yk-z0XYg0SjF@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