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

From Oleksii Kliukin
Subject Re: Prepared transaction releasing locks before deregistering its GID
Date
Msg-id 2AB98E72-430C-4CEF-A9EA-3F183CE2CDD1@hintbits.com
Whole thread Raw
In response to Re: Prepared transaction releasing locks before deregistering its GID  (Oleksii Kliukin <alexk@hintbits.com>)
Responses Re: Prepared transaction releasing locks before deregistering its GID
List pgsql-hackers
Hi,

Oleksii Kliukin <alexk@hintbits.com> wrote:
>
> The approach looks good to me. Surprisingly, I saw no stalled backends
> because of the double acquisition of lock at TwoPhaseGetGXact once I put a
> simple TwoPhaseStateLock right before the "gxact->valid = false” line; I
> will test your patch and post the outcome.

I gave it a spin on the same VM host as shown to constantly reproduce the
issue and observed neither 'identifier already in use' nor any locking
issues over a few dozens of runs, so it looks good to me.

That was HEAD, but since FinishPreparedTransaction seems to be identical
there and on the back branches it should work for PG 10 and 11 as well.

Regards,
Oleksii Kliukin



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Some thoughts on NFS
Next
From: Robert Haas
Date:
Subject: Re: propagating replica identity to partitions