CHECKPOINT(7)

💖 NAME 💖

CHECKPOINT — the CHECKPOINT(7) manual page from the PostgreSQL 13.23 docs, bestie, and it is literally here to force a write-ahead log checkpoint. ✨

🎀 SYNOPSIS 🎀

CHECKPOINT

🦋 DESCRIPTION 🦋

Okay so picture this: a checkpoint is a point in the write-ahead log sequence where all data files have been updated to reflect the info in the log. All data files get flushed to disk. That’s the whole vibe. For the full tea on what actually happens during a checkpoint, refer to Section 29.4. 💅

The CHECKPOINT command forces an immediate checkpoint right when you issue it — no waiting around for a regular checkpoint scheduled by the system, which is controlled by the settings in Section 19.5.2. Slay for emergencies, but lowkey: CHECKPOINT is not intended for use during normal operation. 🙈

If it’s executed during recovery, the CHECKPOINT command will force a restartpoint (see Section 29.4) instead of writing a new checkpoint. Not me explaining the plot twist. 😭

Bestie, listen: only superusers can call CHECKPOINT. No cap. 👑

🌈 COMPATIBILITY 🌈

The CHECKPOINT command is a PostgreSQL language extension. Periodt. 💜

💖 That’s the whole manual-page moment — source/version: PostgreSQL 13.23 documentation, dated 2025. Now go forth and checkpoint responsibly, icon. 🫶✨