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

From tsunakawa.takay@fujitsu.com
Subject RE: A few new options for CHECKPOINT
Date
Msg-id TYAPR01MB2990F066EC4B13B37120C6F3FEFA0@TYAPR01MB2990.jpnprd01.prod.outlook.com
Whole thread Raw
In response to A few new options for CHECKPOINT  ("Bossart, Nathan" <bossartn@amazon.com>)
Responses Re: A few new options for CHECKPOINT  ("Bossart, Nathan" <bossartn@amazon.com>)
List pgsql-hackers
From: Bossart, Nathan <bossartn@amazon.com>
> The main purpose of this patch is to give users more control over their manually
> requested checkpoints or restartpoints.  I suspect the most useful option is
> IMMEDIATE, which can help avoid checkpoint- related IO spikes.  However, I
> didn't see any strong reason to prevent users from also adjusting FORCE and
> WAIT.

I think just IMMEDIATE would suffice, too.  But could you tell us why you got to want to give users more control?
Couldwe know concrete example situations where users want to perform CHECKPOINT with options?
 


Regards
Takayuki Tsunakawa


pgsql-hackers by date:

Previous
From: David Zhang
Date:
Subject: Add table access method as an option to pgbench
Next
From: Andy Fan
Date:
Subject: Re: About adding a new filed to a struct in primnodes.h