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

From Alexander Lakhin
Subject Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY
Date
Msg-id 17622f79-117a-4a44-aa8e-0374e53faaf0@gmail.com
Whole thread Raw
In response to Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY  (Álvaro Herrera <alvherre@kurilemu.de>)
List pgsql-hackers
Hello Álvaro and Mihail,

02.12.2025 15:07, Álvaro Herrera wrote:
Thanks, pushed this one after some more editorialization.

I've discovered that despite removing FIXME (in 90eae926a), the error
"invalid arbiter index list" can still be triggered with:
CREATE TABLE pt (a int PRIMARY KEY) PARTITION BY RANGE (a);
CREATE TABLE p1 PARTITION OF pt FOR VALUES FROM (1) to (2) PARTITION BY RANGE (a);
CREATE TABLE p1_1 PARTITION OF p1 FOR VALUES FROM (1) TO (2);
CREATE UNIQUE INDEX ON ONLY p1 (a);
INSERT INTO p1 VALUES (1) ON CONFLICT (a) DO NOTHING;
ERROR:  XX000: invalid arbiter index list
LOCATION:  ExecInitPartitionInfo, execPartition.c:863

The first commit it produced on with this script is bc32a12e0.

Best regards,
Alexander

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Improve error reporting in 027_stream_regress test
Next
From: Bryan Green
Date:
Subject: Re: [PATCH] Allow complex data for GUC extra.