Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY - Mailing list pgsql-hackers

From Mihail Nikalayeu
Subject Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY
Date
Msg-id CADzfLwWJD9whA0cY8iCqPsk7PeN=KyomqpTXU4B0j3TDuebUyg@mail.gmail.com
Whole thread Raw
In response to Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY  (Mihail Nikalayeu <mihailnikalayeu@gmail.com>)
List pgsql-hackers
Hello, Álvaro!

On Thu, Jan 8, 2026 at 11:08 AM Mihail Nikalayeu
<mihailnikalayeu@gmail.com> wrote:
> I'll try to prepare next set of fixes today/tomorrow:
>
> * In wait_for_idle exit early if we see backend stuck into injection
> point (no sense to wait more, my bad - should be added from the
> start), also reduce timeout to 1/2 of TAP
> * In wait_for_injection_point use 1/2 of TAP timeout.
> * Try to detect install_check in tests and skip instead of whole pack
> * Change year to 2026 :)

Fixes for the fixes are in attachment.

I am not very confident about the second commit, because I am not an
expert in meson/Makefiles.
Some additional explanations are available in commit messages.

Tested with -DCLOBBER_CACHE_ALWAYS=1

I hope this is the last one.

Best regards,
Mikhail.

Attachment

pgsql-hackers by date:

Previous
From: Henson Choi
Date:
Subject: Re: SQL Property Graph Queries (SQL/PGQ)
Next
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: Simplify code building the LR conflict messages