Re: [PATCH] add concurrent_abort callback for output plugin - Mailing list pgsql-hackers

From Ajin Cherian
Subject Re: [PATCH] add concurrent_abort callback for output plugin
Date
Msg-id CAFPTHDY8fPsfisk0iokn_6820MPvfus0Su14RFYzk7zXaLdg0Q@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] add concurrent_abort callback for output plugin  (Markus Wanner <markus.wanner@enterprisedb.com>)
Responses Re: [PATCH] add concurrent_abort callback for output plugin  (Markus Wanner <markus@bluegap.ch>)
List pgsql-hackers


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 
Attachment

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: [PATCH] add concurrent_abort callback for output plugin
Next
From: Amit Kapila
Date:
Subject: Re: Use consistent terminology for tablesync slots.