Re: [HACKERS] logical decoding of two-phase transactions - Mailing list pgsql-hackers

From Petr Jelinek
Subject Re: [HACKERS] logical decoding of two-phase transactions
Date
Msg-id 3cca7c66-2a5e-a3c1-a197-9bb107e0b69f@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] logical decoding of two-phase transactions  (Andres Freund <andres@anarazel.de>)
Responses Re: [HACKERS] logical decoding of two-phase transactions
List pgsql-hackers
On 30/03/18 20:50, Andres Freund wrote:
> Hi,
> 
> On 2018-03-30 23:49:43 +0530, Nikhil Sontakke wrote:
>>> Quick thought: Should be simple to release lock when interacting with network.
>>
>> I don’t think this will be that simple. The network calls will
>> typically happen from inside the plugins and we don’t want to make
>> plugin authors responsible for that.
> 
> You can just throw results away... ;). I'm not even kidding.  We've all
> the necessary access in the callback for writing from a context.
>

You mean, if we detect abort in the write callback, set something in the
context which will make all the future writes noop until it's reset
again after we yield back to the logical decoding?

That's not the most beautiful design I've seen, but I'd be okay with
that, it seems like it would solve all the issues we have with this.

-- 
  Petr Jelinek                  http://www.2ndQuadrant.com/
  PostgreSQL Development, 24x7 Support, Training & Services


pgsql-hackers by date:

Previous
From: Lukas Fittl
Date:
Subject: Re: [HACKERS] Planning counters in pg_stat_statements
Next
From: Andres Freund
Date:
Subject: Re: [HACKERS] logical decoding of two-phase transactions