| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> |
| Cc: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org, alvherre(at)kurilemu(dot)de |
| Subject: | Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes |
| Date: | 2026-08-31 21:34:23 |
| Message-ID: | 264AB6A4-640F-4E4B-99EB-61723CE71C1C@thebuild.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> On Aug 26, 2026, at 00:31, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)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 different behavior in the presence of invalid indexes specifically because it would be a behavior change if we pushed that change to other commands.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zsolt Parragi | 2026-08-31 23:08:44 | Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes |
| Previous Message | Jochen Bandhauer | 2026-08-31 11:20:30 | Re: repack with verbose output: not showing the number of removable row versions when using USING INDEX or CONCURRENTLY option |