Re: Logical replication can lose an update after concurrent index invalidation

From: vignesh C <vignesh21(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, onderkalaci(at)gmail(dot)com
Subject: Re: Logical replication can lose an update after concurrent index invalidation
Date: 2026-09-28 12:20:25
Message-ID: CALDaNm0iYZbfLtjA+O9a3kQTmDeRreK4R-9bzy9GpPGYec7spg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 23 Sept 2026 at 15:26, vignesh C <vignesh21(at)gmail(dot)com> wrote:
>
> On Tue, 22 Sept 2026 at 15:33, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:

The ABI compliance check in buildfarm failed at [1], [2], and [3]
after the patch was committed because the LogicalRepRelMapEntry
structure added the idxisreplident field. However, this does not cause
an ABI break, as the new bool uses existing alignment padding, so the
offsets of existing fields and sizeof(LogicalRepRelMapEntry) remain
unchanged. Here is a patch to document this in
.abi-compliance-history.

[1] - https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=akepa&dt=2026-09-28%2011%3A27%3A04
[2] - https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=akepa&dt=2026-09-28%2011%3A26%3A06
[3] - https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2026-09-28%2011%3A47%3A02

Regards,
Vignesh

Attachment Content-Type Size
v1_REL16-0001-Update-.abi-compliance-history-for-tuple-se.patch application/octet-stream 1017 bytes
v1_REL17-0001-Update-.abi-compliance-history-for-tuple-se.patch application/octet-stream 1017 bytes
v1_REL18-0001-Update-.abi-compliance-history-for-tuple-se.patch application/octet-stream 1.0 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ajin Cherian 2026-09-28 12:20:33 Re: [PATCH] Preserve replication origin OIDs in pg_upgrade
Previous Message Chao Li 2026-09-28 11:49:05 Re: Typo in version check in postgresAcquireSampleRowsFunc