> [!CheckpointerWriteDelay] > <table><tr><td rowspan="4" width="25%"><img src="assets/wl_timeout_checkpointwritedelay.png"></td><td><b>Wait Category</b></td><td>Timeout</td></tr><tr><td><b>Mechanism</b></td><td><code>CheckpointerMain</code></td></tr><tr><td><b>Operations</b></td><td><a href="Operations/ResultSet/Materialize">Materialize</a></td></tr><tr><td><b>Resources</b></td><td><a href="Resources/disk IO">disk IO</a>, <a href="Resources/CPU">CPU</a></td></tr><tr><td colspan="3">This wait event represents the <b>Paced Flushing</b> of the buffer cache. To prevent a "checkpoint spike" from saturating your disk I/O and slowing down user queries, Postgres attempts to spread the checkpoint work over the duration specified by <code>checkpoint_completion_target</code>.</td></tr></table>