Request a Demo
Home   >   mailing lists

Re: Logical replication can lose an update after concurrent index invalidation - Mailing list pgsql-hackers

From vignesh C
Subject Re: Logical replication can lose an update after concurrent index invalidation
Date
Msg-id CALDaNm0iYZbfLtjA+O9a3kQTmDeRreK4R-9bzy9GpPGYec7spg@mail.gmail.com
Whole thread
In response to Re: Logical replication can lose an update after concurrent index invalidation  (vignesh C <vignesh21@gmail.com>)
Responses Re: Logical replication can lose an update after concurrent index invalidation
List pgsql-hackers
Tree view 
On Wed, 23 Sept 2026 at 15:26, vignesh C <vignesh21@gmail.com> wrote:
>
> On Tue, 22 Sept 2026 at 15:33, Amit Kapila <amit.kapila16@gmail.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

pgsql-hackers by date:

Previous
From: Chao Li
Date:
Subject: Re: Typo in version check in postgresAcquireSampleRowsFunc
Next
From: Ajin Cherian
Date:
Subject: Re: [PATCH] Preserve replication origin OIDs in pg_upgrade