Re: CheckpointStartLock starvation - Mailing list pgsql-hackers

From Tom Lane
Subject Re: CheckpointStartLock starvation
Date
Msg-id 26321.1175608099@sss.pgh.pa.us
Whole thread Raw
In response to Re: CheckpointStartLock starvation  (Heikki Linnakangas <heikki@enterprisedb.com>)
Responses Re: CheckpointStartLock starvation  (Heikki Linnakangas <heikki@enterprisedb.com>)
List pgsql-hackers
Heikki Linnakangas <heikki@enterprisedb.com> writes:
> Tom Lane wrote:
>> Nor will that work for prepared xacts --- you don't want to wait for the
>> eventual commit, only for PREPARE TRANSACTION to exit its critical
>> section.

> PREPARE TRANSACTION wouldn't set the flag in MyProc; there's no clog 
> changes to protect from at that point. It would be set in 
> RecordTransactionCommitPrepared when we're really committing. Just like 
> we use the CheckpointStartLock today.

Indeed --- you'd better take another look at where we use the
CheckpointStartLock today.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Marko Kreen"
Date:
Subject: Re: PL/Python warnings in CVS HEAD
Next
From: Heikki Linnakangas
Date:
Subject: Re: CheckpointStartLock starvation