Re: [PATCH] add concurrent_abort callback for output plugin

Ajin Cherian <itsajin@gmail.com>

From: Ajin Cherian <itsajin@gmail.com>
To: Markus Wanner <markus.wanner@enterprisedb.com>
Cc: Amit Kapila <amit.kapila16@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-03-30T09:12:57Z
Lists: pgsql-hackers

Attachments

On Tue, Mar 30, 2021 at 7:10 PM Markus Wanner <
markus.wanner@enterprisedb.com> wrote:

> On 30.03.21 09:39, Ajin Cherian wrote:
> > Where do you suggest this be documented? From an externally visible
> > point of view, I dont see much of a surprise.
>
>
>
> So I suggest to document this as a caveat for the prepare callback,
> because with this patch that's the callback which may be invoked for an
> incomplete transaction without the output plugin knowing.
>

I found some documentation that already was talking about concurrent aborts
and updated that.
Patch attached.

regards,
Ajin Cherian
Fujitsu Australia

Commits

  1. Avoid sending prepare multiple times while decoding.

  2. Ensure to send a prepare after we detect concurrent abort during decoding.