Skip site navigation (1) Skip section navigation (2)

Re: CheckpointStartLock starvation

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: CheckpointStartLock starvation
Date: 2007-04-03 13:48:19
Message-ID: 26321.1175608099@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Heikki Linnakangas <heikki(at)enterprisedb(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Heikki LinnakangasDate: 2007-04-03 13:51:52
Subject: Re: CheckpointStartLock starvation
Previous:From: Marko KreenDate: 2007-04-03 13:46:44
Subject: Re: PL/Python warnings in CVS HEAD

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group