checkpoint_completion_target
No restart — takes effect on reloadtuned by pgconfiguratorratio (0–1)
How much of the interval to spread checkpoint writes over, smoothing I/O.
What pgconfigurator would set
32 GB · 8 vCPU · NVMe · OLTP
Computing…
Tune for your exact server → /tunecomputed in your browser · nothing uploaded
What it does
checkpoint_completion_target controls how gradually a checkpoint's dirty-page writes are spread across the time until the next checkpoint. A value near 1.0 dribbles the writes out slowly, avoiding a sharp I/O spike at checkpoint time.
How to tune it
Modern PostgreSQL defaults to 0.9, which is what you want in almost all cases — it spreads writes over 90% of the interval. There's rarely a reason to lower it. (Older guides recommended raising it from 0.5; that's already done by default now.)