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 15:53:03
Message-ID: CADzfLwUBeyhOB5=4Lyn3yHUVDM5jD3mVEK15jKYGBtZw74DEHg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello, Miłosz!

> Any thoughts on moving the 'idxRel->rd_index->indisvalid' check into 'IsIndexUsableForReplicaIdentityFull()' itself?

I initially thought about that approach too, but an assertion also
uses that check.
This is explained in the commit message:

> Skip invalid indexes, as the planner does. The test belongs here rather
> than in IsIndexUsableForReplicaIdentityFull(), whose other caller is an
> assertion that would then trip over an index DROP INDEX CONCURRENTLY has
> just invalidated but that still finds tuples fine.

Regards,
Mikhail

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2026-08-24 16:06:48 Re: postgres_fdw: Fix flaky push down FUNCTION RTE test
Previous Message Михаил Купцов 2026-08-24 15:34:29 Changing client-side behavior regarding Certificate Revocation Lists (CRL)