Tom Lane wrote:
> Heikki Linnakangas <heikki(at)enterprisedb(dot)com> writes:
>> As a proposed fix, instead of acquiring the CheckpointStartLock in 
>> RecordTransactionCommit, we set a flag in MyProc saying "commit in 
>> progress". Checkpoint will scan through the procarray and make note of 
>> any commit in progress transactions, after computing the new redo record 
>> ptr, and wait for all of them to finish before flushing clog.
> 
> What sort of "wait for finish" mechanism do you have in mind?  While
> I've always thought CheckpointStartLock is a pretty ugly solution,
> I'm not sure the above is better.

I was thinking of XactLockTableWait.

-- 
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com

In response to

• Re: CheckpointStartLock starvation at 2007-04-02 19:46:04 from Tom Lane

Responses

• Re: CheckpointStartLock starvation at 2007-04-02 21:32:52 from Tom Lane

pgsql-hackers by date

Next:	From: Bruce Momjian	Date: 2007-04-02 20:59:08
	Subject: Re: [PATCHES] Use non-deprecated APIs for dynloader/darwin.c
Previous:	From: Mark Dilger	Date: 2007-04-02 20:50:36
	Subject: Re: Bug in UTF8-Validation Code?