| From: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
|---|---|
| To: | Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Noah Misch <noah(at)leadboat(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY |
| Date: | 2025-12-06 06:00:01 |
| Message-ID: | 17622f79-117a-4a44-aa8e-0374e53faaf0@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bryan Green | 2025-12-06 07:08:47 | Re: [PATCH] Allow complex data for GUC extra. |
| Previous Message | Michael Paquier | 2025-12-06 05:45:13 | Re: Improve error reporting in 027_stream_regress test |