Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY

From: Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com>
To: Alexander Lakhin <exclusion(at)gmail(dot)com>
Cc: Álvaro Herrera <alvherre(at)kurilemu(dot)de>, 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: 2026-01-19 22:59:41
Message-ID: CADzfLwUzCDiB57oBW2Zx+Tud=4WDCOUQhPfcnshLDccDkXdRrA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello, Alexander!

Thanks for your investigation!

I was able to reproduce it locally, not easily, but possible.

It fails with the state then we have 2 indexes
(leaf_part_rri->ri_NumIndices=2) and EACH OF them have an ancestor. So,
both of them are added as arbiters.

Not sure if it correct behavior or something is broken in another place.

I'll try to dive deeper a little bit later.

Best regards,
Mikhail.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2026-01-19 23:07:56 Re: Patch: dumping tables data in multiple chunks in pg_dump
Previous Message Zsolt Parragi 2026-01-19 22:40:16 Re: Proposal: Adding compression of temporary files