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

From Amit Kapila
Subject Re: Logical replication can lose an update after concurrent index invalidation
Date
Msg-id CAA4eK1+gV1Y6PefgBxpoJZm8Nn1FEBpSi9wfv8cQ+hGLhCLTPQ@mail.gmail.com
Whole thread
In response to Re: Logical replication can lose an update after concurrent index invalidation  (vignesh C <vignesh21@gmail.com>)
List pgsql-hackers
On Mon, Sep 28, 2026 at 8:20 AM vignesh C <vignesh21@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.
>

Thanks, I've pushed the patches.

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: "Kevin Rocker"
Date:
Subject: Re: [PATCH] Fix vacuum_delay_point happening inside lock
Next
From: "Tristan Partin"
Date:
Subject: Re: Add counted_by attribute