Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY

From: Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com>
To: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: Alexander Lakhin <exclusion(at)gmail(dot)com>, 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-26 21:33:00
Message-ID: CADzfLwWzxd6aO5UoE2dUObm4CUaD5yX=0cZKjETrpipHfUHyPg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello!

> Great, many thanks for this. The commit message looks quite good, but I
> decided to rewrite the comment in the code. What do you think of this?

Much better.

> (There's also a typo fix for one of the previous commits)
:) Interesting how it went so far.

> Hmm, I think a syscache on (inhrelid, inhseqno) is a bit weird. This
> might be okay, but I'm not sure, and I don't think we absolutely need
> this right now. That is to say, I'm not rejecting this, but I'm not
> going to pursue getting it pushed for now.

I'll try to measure some impact later.

Best regards,
Mikhail.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2026-01-26 22:17:08 Re: unclear OAuth error message
Previous Message Masahiko Sawada 2026-01-26 21:24:27 RepOrigin vs. replorigin