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-02 19:46:04
Message-ID: 26934.1175543164@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zdenek Kotala 2007-04-02 19:48:29 Re: Is this portable?
Previous Message Bruce Momjian 2007-04-02 19:29:04 Re: Is this portable?