Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes
Date: 2026-07-27 11:05:50
Message-ID: amc6yk-z0XYg0SjF@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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/

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Álvaro Herrera 2026-07-27 11:13:30 Re: BUG #19580: Can not FINALIZE detach partition. Table in stuck
Previous Message Rui Zhao 2026-07-26 17:25:14 Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table