Tom Lane wrote:
> Heikki Linnakangas <heikki(at)enterprisedb(dot)com> writes:
>> Tom Lane wrote:
>>> What sort of "wait for finish" mechanism do you have in mind?
>> I was thinking of XactLockTableWait.
> Ugh. I don't think the bgwriter can participate in heavyweight-lockmgr
> operations, or should become able to.
Oh, good point.
I suppose we could just poll and sleep, checkpoint is a heavy operation
anyway so a little delay wouldn't hurt.
> 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
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.
In response to
pgsql-hackers by date
|Next:||From: Marko Kreen||Date: 2007-04-03 08:56:16|
|Subject: Re: PL/Python warnings in CVS HEAD|
|Previous:||From: Zeugswetter Andreas ADI SD||Date: 2007-04-03 08:21:11|
|Subject: Re: Modifying TOAST thresholds|