From: Alexander Lakhin <exclusion@gmail.com>
To: Álvaro Herrera <alvherre@kurilemu.de>
To: Mihail Nikalayeu <mihailnikalayeu@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: Noah Misch <noah@leadboat.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY
Date: Sat, 6 Dec 2025 08:00:01 +0200
Message-ID: <17622f79-117a-4a44-aa8e-0374e53faaf0@gmail.com> (raw)
In-Reply-To: <202512021255.r3ouzsfyxg5r@alvherre.pgsql>
References: <202512021255.r3ouzsfyxg5r@alvherre.pgsql>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: exclusion@gmail.com, alvherre@kurilemu.de, mihailnikalayeu@gmail.com, michael@paquier.xyz, noah@leadboat.com
Subject: Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY
In-Reply-To: <17622f79-117a-4a44-aa8e-0374e53faaf0@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox