Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
Cc: Christophe Pettus <xof(at)thebuild(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, rmt(at)lists(dot)postgresql(dot)org
Subject: Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes
Date: 2026-09-13 12:27:13
Message-ID: aqaV_h_4n0OnYOvT@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Pushed this with minor tweaks.

There was no hard consensus on this approach, just a couple of favorable
votes, so I guess it's still possible that somebody will object to this
approach. I'll keep the open item for a couple of days, just in case.

Thanks

--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"No es bueno caminar con un hombre muerto"

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message shihao zhong 2026-09-14 02:35:00 Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes
Previous Message Ayush Tiwari 2026-09-13 06:36:13 Re: BUG #19684: Assertion in tuplesort_begin_heap() falsified by parallel plan with sort

Browse pgsql-hackers by date

  From Date Subject
Next Message Álvaro Herrera 2026-09-13 12:52:54 Re: CLUSTER progress: wrong index_rebuild_count for tables with TOAST
Previous Message Dean Rasheed 2026-09-13 12:16:20 Re: [BUG] ON CONFLICT DO UPDATE SET x = EXCLUDED.<virtual-generated-column> errors or silently writes NULL