Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY

From: Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com>
To: Hannu Krosing <hannuk(at)google(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-11-28 18:42:31
Message-ID: CADzfLwVS46YE5qSFPZYaDY9eVJyiOTjsuFADxdeE6_T46x-8eA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi!

On Fri, Nov 28, 2025 at 7:09 PM Hannu Krosing <hannuk(at)google(dot)com> wrote:
> Please also check my (very raw) proposal in the thread "Revisiting
> {CREATE INDEX, REINDEX} CONCURRENTLY improvements"
>
> TL;DR - use logical decoding for adding index entries for tuples added
> during CIC.

No, the current issue is caused by another reason - it is more about
switching from old to new index.

Best regards,
Mikhail.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2025-11-28 18:57:14 Re: should we have a fast-path planning for OLTP starjoins?
Previous Message Mihail Nikalayeu 2025-11-28 18:40:45 Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements