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

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: vignesh C <vignesh21(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 15:15:22
Message-ID: CAA4eK1+gV1Y6PefgBxpoJZm8Nn1FEBpSi9wfv8cQ+hGLhCLTPQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Sep 28, 2026 at 8:20 AM vignesh C <vignesh21(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.
>

Thanks, I've pushed the patches.

--
With Regards,
Amit Kapila.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tristan Partin 2026-09-28 15:23:58 Re: Add counted_by attribute
Previous Message Kevin Rocker 2026-09-28 15:07:52 Re: [PATCH] Fix vacuum_delay_point happening inside lock