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: 2025-12-01 11:27:46
Message-ID: CADzfLwUS3qfk_YVT-Kx_14g3LKpU58FQxaLudCECkz1OCH3dYA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello!

On Sun, Nov 30, 2025 at 6:26 PM Mihail Nikalayeu
<mihailnikalayeu(at)gmail(dot)com> wrote:
> I think it is better to implement something in isolationtester to
> natively support the case from [0] (in such case we don't need NOTICE
> on .pre-invalidate-catalog-snapshot-end).

I think I have implemented a better solution - without any additional NOTICE.
It just actually waits for the other backend to hang on the injection point.

Attached (together with other changes).

Attachment Content-Type Size
v16-0002-Revert-Doc-cover-index-CONCURRENTLY-causing-erro.patch text/plain 1.9 KB
v16-0003-Refactor-test-to-avoid-any-additional-injection-.patch text/plain 18.4 KB
v16-0001-Modify-the-ExecInitPartitionInfo-function-to-con.patch text/plain 18.3 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Aleksander Alekseev 2025-12-01 11:48:23 Re: Migrate to autoconf 2.72?
Previous Message Soumya S Murali 2025-12-01 11:18:56 [PATCH] Expose checkpoint reason to completion log messages.