Re: A few new options for CHECKPOINT - Mailing list pgsql-hackers

From Laurenz Albe
Subject Re: A few new options for CHECKPOINT
Date
Msg-id 1b097b167ecdcc903962cbe55526cdfa2c4e97cb.camel@cybertec.at
Whole thread Raw
In response to Re: A few new options for CHECKPOINT  (Bernd Helmle <mailings@oopsware.de>)
Responses Re: A few new options for CHECKPOINT  ("Bossart, Nathan" <bossartn@amazon.com>)
List pgsql-hackers
On Wed, 2020-11-25 at 11:41 +0100, Bernd Helmle wrote:
> Am Mittwoch, den 25.11.2020, 13:47 +0900 schrieb Michael Paquier:
> 
> > I can see the use case for IMMEDIATE, but I fail to see the use cases
> > for WAIT and FORCE.  CHECKPOINT_FORCE is internally implied for the
> > end-of-recovery and shutdown checkpoints.  WAIT could be a dangerous
> > thing if disabled, as clients could pile up requests to the
> > checkpointer for no real purpose.
> 
> Wouldn't it be more convenient to use "FAST" for immediate checkpoint,
> defaulting to "FAST ON"? That would be along the parameter used in the
> streaming protocol command BASE_BACKUP, where "FAST" disables lazy
> checkpointing.

+1

That would also match pg_basebackup's "-c fast|spread".

Yours,
Laurenz Albe




pgsql-hackers by date:

Previous
From: Konstantin Knizhnik
Date:
Subject: Re: Implementing Incremental View Maintenance
Next
From: Konstantin Knizhnik
Date:
Subject: Transaction isolation and table contraints