CHECKPOINT(7)

✨ CHECKPOINT(7) ✨

okay bestie, this is CHECKPOINT(7) from the PostgreSQL 17.11 Documentation — yes, the manual page, and yes, it’s giving “force a write-ahead log checkpoint” energy 💅

---

🎀 NAME 🎀

CHECKPOINT — force a write-ahead log checkpoint ✨

---

🌸 SYNOPSIS 🌸

CHECKPOINT

---

💖 DESCRIPTION 💖

So, a checkpoint is a point in the write-ahead log sequence at which all data files have been updated to reflect the information in the log. All data files will be flushed to disk. Refer to Section 28.5 for more details about what happens during a checkpoint 👑

The CHECKPOINT command forces an immediate checkpoint when the command is issued, without waiting for a regular checkpoint scheduled by the system — that scheduling is controlled by the settings in Section 19.5.2 🫶

heads up, bestie: CHECKPOINT is not intended for use during normal operation 💀

If executed during recovery, the CHECKPOINT command will force a restartpoint (see Section 28.5) rather than writing a new checkpoint 🌈

Only superusers or users with the privileges of the pg_checkpoint role can call CHECKPOINT 🔐

---

🦋 COMPATIBILITY 🦋

The CHECKPOINT command is a PostgreSQL language extension ✨

---

xoxo, bestie 💖 this cutie is brought to you by PostgreSQL 17.11, dated 2026, signing off from the footer with a little CHECKPOINT(7) sparkle 🎀🫶