| 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-28 06:16:07 |
| Message-ID: | amhIwN9DHA1NEPxN@alvherre.pgsql |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2026-Jul-27, Zsolt Parragi wrote:
> > Wouldn't it make more sense to just ignore invalid indexes and not build
> > anything at all for them?
>
> I followed what REPACK/VACUUM FULL does - it similarly rebuilds
> invalid indexes, shouldn't we keep the two consistent?
I don't know. Maybe rebuilding invalid indexes is pointless. Don't you
think so? An invalid index can never be turned valid, so why spend
effort in building it at all?
> And by skipping you mean that we should create an empty index instead
> when repack sees an invalid index?
I mean we should just ignore all invalid indexes.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"¿Cómo puedes confiar en algo que pagas y que no ves,
y no confiar en algo que te dan y te lo muestran?" (Germán Poo)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zsolt Parragi | 2026-07-28 09:37:16 | Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes |
| Previous Message | Ayush Tiwari | 2026-07-28 05:48:13 | Re: BUG #19579: Wrong results regression |