Re: CheckpointLock needed in CreateCheckPoint()?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Amul Sul <sulamul(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: CheckpointLock needed in CreateCheckPoint()?
Date: 2021-01-18 21:42:46
Message-ID: CA+Tgmobkd99XJKXqDQpxi=GV1oahBrHTWT9_f6dg=T7kZ7apyg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jan 18, 2021 at 3:25 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> If memory serves, the reason for the lock was that the CHECKPOINT
> command used to run the checkpointing code directly in the calling
> backend, so we needed it to keep more than one process from doing
> that at once. AFAICS, it's no longer possible for more than one
> process to try to run that code concurrently, so we shouldn't need
> the lock anymore.

Interesting. I think that must have been a *very* long time ago.
Perhaps 076a055acf3c55314de267c62b03191586d79cf6 from 2004?

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-01-18 21:48:04 Odd, intermittent failure in contrib/pageinspect
Previous Message Robert Haas 2021-01-18 21:38:47 Re: Key management with tests