Re: [PATCH] add concurrent_abort callback for output plugin

From: Ajin Cherian <itsajin(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Markus Wanner <markus(dot)wanner(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] add concurrent_abort callback for output plugin
Date: 2021-03-29 11:02:34
Message-ID: CAFPTHDafhRwJOY-yxHnXWiss7GBpumadsCSVi6+XwGE0xp3NCQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Mar 29, 2021 at 8:33 PM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:

> On Mon, Mar 29, 2021 at 12:36 PM Markus Wanner
> <markus(dot)wanner(at)enterprisedb(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message vignesh C 2021-03-29 11:04:23 Re: [PATCH] Provide more information to filter_prepare
Previous Message Matthias van de Meent 2021-03-29 10:57:55 Re: Calendar support in localization