Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes - Mailing list pgsql-bugs

From Christophe Pettus
Subject Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes
Date
Msg-id 264AB6A4-640F-4E4B-99EB-61723CE71C1C@thebuild.com
Whole thread
In response to Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes  (Zsolt Parragi <zsolt.parragi@percona.com>)
List pgsql-bugs

> On Aug 26, 2026, at 00:31, Zsolt Parragi <zsolt.parragi@percona.com> wrote:
> Not allowing these commands (consistently) to work on tables with
> invalid indexes is an option, but then that should be consistent
> across all similar commands, and it will be a behavior change for
> normal vacuum too.

I think your statement has its own answer embedded in it: It's acceptable for REPACK, a brand-new command, to have
differentbehavior in the presence of invalid indexes specifically because it would be a behavior change if we pushed
thatchange to other commands. 


pgsql-bugs by date:

Previous
From: Andrey Rachitskiy
Date:
Subject: Re: BUG #19487: Error while executing SQL query involving XML parsing
Next
From: PG Bug reporting form
Date:
Subject: BUG #19652: to_number() silently truncates over-length integers