liveBook · Manning

Base backup

As explained in PostgreSQL Mistakes and How to Avoid Them

A base backup is a physical copy of a PostgreSQL database cluster taken at a specific point in time for restoration.

A base backup is a physical copy of a PostgreSQL database cluster captured at a specific point in time for restoration. Do not confuse it with a logical dump: pg_dump extracts one database through a consistent snapshot, while pg_dumpall loops across databases and still cannot guarantee cross-database consistency. section 9.2

A backup strategy built only around logical dumps has practical limits:

  • A pg_dump backup restores to an empty database, but captures only the data available when that dump was taken. section 9.2
  • Daily backups can lose transactions committed after the last backup, including changes made before an afternoon mistake or outage. section 9.2
  • Separate dumps of interdependent databases do not provide a consistent shared recovery point while both databases are running. section 9.2

How PostgreSQL Mistakes and How to Avoid Them covers it

How deep it goes
Defines a point-in-time physical copy, but stops short of explaining its capture procedure or recovery mechanics.
Examples
Contrasts physical base backups with pg_dump snapshots and pg_dumpall’s per-database backup loop.
What it assumes
Assumes PostgreSQL database and cluster concepts while establishing the distinction between logical dumps and physical copies.
What you can do after
Evaluate whether a PostgreSQL backup plan can restore the cluster consistently and identify transaction-loss limits.
How it connects
Connects base backups with PostgreSQL clusters, restoration, pg_dump, pg_dumpall, snapshots, and point-in-time recovery.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of PostgreSQL Mistakes and How to Avoid Them. The section links point to the parts of the book it draws on.