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

From Mihail Nikalayeu
Subject Re: Logical replication can lose an update after concurrent index invalidation
Date
Msg-id CADzfLwX_g63_4jMuRGwwo6tWsTSZ2C0+7Bbgm0ctkNovfaV4aw@mail.gmail.com
Whole thread
In response to Logical replication can lose an update after concurrent index invalidation  (Mihail Nikalayeu <mihailnikalayeu@gmail.com>)
Responses Re: Macro redefinition warning after aeb07c55fab5c17a600b77ffcdc3b71425d6a8e7
Re: Macro redefinition warning after aeb07c55fab5c17a600b77ffcdc3b71425d6a8e7
Re: Logical replication can lose an update after concurrent index invalidation
List pgsql-hackers
Hello!

> RelationFindReplTupleByIndex() is an extern function declared in a
> core executor header (executor.h). Adding a new parameter
> (isIdxSafeToSkipDuplicates) changes its calling convention.
> Similarly I'm not sure of adding isidentity to LogicalRepRelMapEntry
> in back branches as it will change its size and memory layout.

Yep, fair, thanks.

In v2 I put a new flag into padding and used the same pattern for the
function as in 9e47718250d.

abidiff now shows that:

'struct LogicalRepRelMapEntry' changed:
  type size hasn't changed
  1 data member insertion:
    'bool isidentity', at offset 89 (in bytes)

I think it is ok for such a type. I couldn't find any usage in extensions.

Should we update .abi-compliance-history in such a case?

Best regards,
Mikhail.

Attachment

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: [PATCH] Release replication slot on error in SQL-callable slot functions
Next
From: Andrew Dunstan
Date:
Subject: Re: locale / encoding / meson cleanup