| From: | Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> |
|---|---|
| To: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes |
| Date: | 2026-08-13 21:37:25 |
| Message-ID: | CAN4CZFMt0uYQPrB4Ey3nxVJZB1phf_iPz6Up6WW=ZW5WrYzvSw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> I'll create a patch for that approach, but it is a bit more complex than v1.
It turned out not to be that complex, attached v2.
One thing to point out is that this is a slight behavior change for
REINDEX TABLE. We could avoid that, but the current behavior doesn't
seem to be documented anywhere, and this version seems more consistent
to me.
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-Don-t-rebuild-invalid-indexes-that-are-not-ready-.patch | application/octet-stream | 21.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zsolt Parragi | 2026-08-13 22:52:00 | Re: COPY TO regression with psql -c |
| Previous Message | Tom Lane | 2026-08-13 20:44:35 | Re: COPY TO regression with psql -c |