Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY
| От | Alexander Lakhin |
|---|---|
| Тема | Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY |
| Дата | |
| Msg-id | 17622f79-117a-4a44-aa8e-0374e53faaf0@gmail.com обсуждение исходный текст |
| Ответ на | Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY (Álvaro Herrera <alvherre@kurilemu.de>) |
| Ответы |
Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY
|
| Список | pgsql-hackers |
Hello Álvaro and Mihail,
02.12.2025 15:07, Álvaro Herrera wrote:
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 по дате отправления: