Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY - Mailing list pgsql-hackers

From Álvaro Herrera
Subject Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY
Date
Msg-id 202512080955.y7zzghv4vag2@alvherre.pgsql
Whole thread Raw
In response to Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY  (Mihail Nikalayeu <mihailnikalayeu@gmail.com>)
Responses Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY
List pgsql-hackers
On 2025-Dec-06, Mihail Nikalayeu wrote:

> From my perspective, the correct solution - is to just remove the
> error message, because it looks obsolete now.

Rereading this -- did you mean to propose that a possible fix was to
remove the "invalid arbiter index list" error?  I had understood
something different.

Your idea downthread of changing the way that check works (so that we
don't throw an error in this case, but we continue to double-check that
the arbiter list is sensible) sounds reasonable to me.  Do you want to
propose a specific check for it?

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/
<inflex> really, I see PHP as like a strange amalgamation of C, Perl, Shell
<crab> inflex: you know that "amalgam" means "mixture with mercury",
       more or less, right?
<crab> i.e., "deadly poison"



pgsql-hackers by date:

Previous
From: Amul Sul
Date:
Subject: Re: alter check constraint enforceability
Next
From: Heikki Linnakangas
Date:
Subject: Re: 64-bit wait_event and introduction of 32-bit wait_event_arg