Re: Prepared transaction releasing locks before deregistering its GID - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Prepared transaction releasing locks before deregistering its GID
Date
Msg-id 20190219040706.GA17530@alvherre.pgsql
Whole thread Raw
In response to Re: Prepared transaction releasing locks before deregistering its GID  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Prepared transaction releasing locks before deregistering its GID  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On 2019-Feb-19, Michael Paquier wrote:

> diff --git a/src/include/access/twophase.h b/src/include/access/twophase.h
> index 6228b091d8..2dcd08e9fa 100644
> --- a/src/include/access/twophase.h
> +++ b/src/include/access/twophase.h
> @@ -34,7 +34,7 @@ extern void TwoPhaseShmemInit(void);
>  extern void AtAbort_Twophase(void);
>  extern void PostPrepare_Twophase(void);
>  
> -extern PGPROC *TwoPhaseGetDummyProc(TransactionId xid);
> +extern PGPROC *TwoPhaseGetDummyProc(TransactionId xid, bool lock_held);
>  extern BackendId TwoPhaseGetDummyBackendId(TransactionId xid);
>  
>  extern GlobalTransaction MarkAsPreparing(TransactionId xid, const char *gid,

Hmm, ABI break ...

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: "Higuchi, Daisuke"
Date:
Subject: [Bug Fix] ECPG: could not use set xxx to default statement
Next
From: Tom Lane
Date:
Subject: Re: [Bug Fix] ECPG: could not use set xxx to default statement