Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: "Mihail Nikalayeu" <mihailnikalayeu(at)gmail(dot)com>
Cc: "Andres Freund" <andres(at)anarazel(dot)de>, "Michael Paquier" <michael(at)paquier(dot)xyz>, "Noah Misch" <noah(at)leadboat(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY
Date: 2026-01-08 00:18:50
Message-ID: bceabf7c-c4a1-4f76-ab0e-b64186913bfe@app.fastmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


>> Special tricks to handle forced-cache release builds included too.
>
> I ran the test in this mode, and it passes fine.

Hmm, it timed out in prion, which runs this "special tricks" code. (I did change the hardcoded timeouts you had to the TAP framework one, but I also made it sleep 0.1s rather than 1s). It is kinda slow on my laptop, though it doesn't time out. But this failure doesn't surprise me. I suspect we need to make the timeout higher.

--
Álvaro Herrera

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2026-01-08 00:24:38 Re: psql: Add tab completion for \copy pstdin and pstdout
Previous Message Michael Paquier 2026-01-08 00:07:01 Re: A small problem when rehashing catalog cache