Re: Apply worker can pick an invalid index for REPLICA IDENTITY FULL lookups

From: Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com>
To: Miłosz Bieniek <bieniek(dot)milosz(at)proton(dot)me>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, onderkalaci(at)gmail(dot)com
Subject: Re: Apply worker can pick an invalid index for REPLICA IDENTITY FULL lookups
Date: 2026-08-24 20:50:45
Message-ID: CADzfLwXt4yDu_w08EcprCggsbSfmmqUybWSk7Y6Asnyn4YyQ+A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi!

> I was wondering if there is a way (and whether it even makes sens
> to make this test fail faster?

I was thinking about that too, so I decided to keep it that way
(aligned with other tests).
Adding some special tricks will make the test too narrow for a
particular scenario.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexandre Felipe 2026-08-24 21:01:43 Re: [PATCH] bufmgr: tighten LWLock:BufferMapping on InvalidateBuffer
Previous Message WGH 2026-08-24 20:35:57 Confusing behaviour of UPDATE together with FOR UPDATE subquery