| From: | Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | REPACK (CONCURRENTLY) doesn't handle invalid indexes |
| Date: | 2026-07-21 10:22:53 |
| Message-ID: | CAN4CZFO5A3YE0Dd-bn7eKrB20pECO3=U0wKg1z2rO=DxgWJJHQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Hello,
While testing REPACK, I noticed that REPACK (CONCURRENTLY) fails with
invalid unique indexes, while the non-concurrent version handles them.
The attached patch mirrors this handling for CONCURRENTLY: constraints
won't be enforced for invalid indexes.
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Don-t-let-invalid-indexes-break-REPACK-CONCURRENTLY.patch | application/octet-stream | 8.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Japin Li | 2026-07-21 10:23:36 | Re: 回复: pg_restore error with partitioned table having exclude constraint |
| Previous Message | Andrey Borodin | 2026-07-21 09:55:11 | Re: Two bugs around ALTER TYPE |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nitin Jadhav | 2026-07-21 10:47:17 | Re: Change checkpoint‑record‑missing PANIC to FATAL |
| Previous Message | Japin Li | 2026-07-21 10:16:27 | Fix optind handling inconsistency in getopt_long() for missing argument |