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

From Michael Paquier
Subject Re: Prepared transaction releasing locks before deregistering its GID
Date
Msg-id 20190219115431.GX15532@paquier.xyz
Whole thread Raw
In response to Re: Prepared transaction releasing locks before deregistering its GID  (Oleksii Kliukin <alexk@hintbits.com>)
List pgsql-hackers
On Tue, Feb 19, 2019 at 10:59:33AM +0100, Oleksii Kliukin wrote:
> Michael Paquier <michael@paquier.xyz> wrote:
>> If you run two transactions in parallel using your script, the second
>> transaction would wait at LOCK time until the first transaction
>> releases its locks with the COMMIT PREPARED.
>
> That is the desired outcome, right?

Yes, that is the correct one in my opinion, and we should not have GID
conflicts when running the scenario you provided upthread.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: Protect syscache from bloating with negative cache entries
Next
From: Tomas Vondra
Date:
Subject: Re: Speed up transaction completion faster after many relations areaccessed in a transaction