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 CAFPTHDafhRwJOY-yxHnXWiss7GBpumadsCSVi6+XwGE0xp3NCQ@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] add concurrent_abort callback for output plugin  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: [PATCH] add concurrent_abort callback for output plugin  (Markus Wanner <markus.wanner@enterprisedb.com>)
List pgsql-hackers


On Mon, Mar 29, 2021 at 8:33 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
On Mon, Mar 29, 2021 at 12:36 PM Markus Wanner
<markus.wanner@enterprisedb.com> wrote:
>
> On 27.03.21 07:37, Amit Kapila wrote:
> > Isn't it better to send prepare from the publisher in such a case so
> > that subscribers can know about it when rollback prepared arrives?

Nice catch, Markus.
Interesting suggestion Amit. Let me try and code this.

regards,
Ajin Cherian
Fujitsu Australia

 

pgsql-hackers by date:

Previous
From: Matthias van de Meent
Date:
Subject: Re: Calendar support in localization
Next
From: vignesh C
Date:
Subject: Re: [PATCH] Provide more information to filter_prepare