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

From Andres Freund
Subject Re: [HACKERS] logical decoding of two-phase transactions
Date
Msg-id 20180330185037.ehgvu4lplcgwekqr@alap3.anarazel.de
Whole thread Raw
In response to Re: [HACKERS] logical decoding of two-phase transactions  (Nikhil Sontakke <nikhils@2ndquadrant.com>)
Responses Re: [HACKERS] logical decoding of two-phase transactions  (Petr Jelinek <petr.jelinek@2ndquadrant.com>)
List pgsql-hackers
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.


> > Could also have abort signal lockers.
> 
> With the decodegroup locking we do have access to all the decoding backend pids. So we could signal them. But am not
suresignaling will work if the plugin is in the midst of a network
 
> Call. 

All walsender writes are nonblocking, so that's not an issue.

Greetings,

Andres Freund


pgsql-hackers by date:

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