Technologies/PostgreSQL/checkpoint_timed
PostgreSQLPostgreSQLMetric

checkpoint_timed

Number of scheduled checkpoints
Dimensions:None
Available on:DatadogDatadog (1)Native (1)PrometheusPrometheus (1)
Interface Metrics (3)
DatadogDatadog
The number of scheduled checkpoints that were performed.
Dimensions:None
Native
Number of scheduled checkpoints
Dimensions:None
PrometheusPrometheus
Number of scheduled checkpoints that have been performed
Dimensions:None
Sources
postgresql.bgwriter.checkpoints_timedgithub.com
checkpoints_timedgithub.com
stat_bgwriter_checkpoints_timed_totalgithub.com

Technical Annotations (8)

Configuration Parameters (4)
checkpoint_timeout
controls time-based checkpoint frequency
max_wal_size
controls size-based checkpoint triggering
checkpoint_completion_target
spreads checkpoint I/O over time
shared_buffers
CLI Commands (2)
gcloud sql instances patch INSTANCE_NAME --database-flags=checkpoint_timeout=900Attempt to set checkpoint timeout (may be silently capped or rejected)
SELECT checkpoints_timed, checkpoints_req, buffers_checkpoint, buffers_clean FROM pg_stat_bgwriter;Monitor checkpoint behavior to verify if tuning changes took effect
Technical References (2)
checkpointconceptWALcomponent
Related Insights (3)
Checkpoint frequency and duration impact write performancewarning
▸
Checkpoint frequency exceeds sustainable ratewarning

Frequent checkpoints cause I/O spikes and performance hiccups. When requested checkpoints (checkpoint_req) significantly exceed timed checkpoints (checkpoint_timed), it indicates max_wal_size is too low or write workload is too high.

▸
Cloud SQL flag restrictions prevent PostgreSQL checkpoint tuning for write workloadswarning

Cloud SQL restricts modification of critical PostgreSQL checkpoint parameters (checkpoint_timeout, max_wal_size) to prevent storage issues. This prevents standard PostgreSQL tuning for write-heavy workloads, causing frequent checkpoint I/O spikes that would normally be mitigated by extending checkpoint intervals.

▸