Cookbook recipe

pg_dump vs physical base backup: choosing

Applies to PostgreSQL 13–17 Last reviewed May 2026 Grounded in source
Estimated investigation4 min

Scenario

You are not sure whether to back up with pg_dump or a physical base backup. They solve different problems. Diagnose it Logical dump of one database: pg_dump -Fc -d app -f app.dump -- physical base backup…

Investigation Path

You are not sure whether to back up with pg_dump or a physical base backup. They solve different problems.

Diagnose it

Logical dump of one database:

pg_dump -Fc -d app -f app.dump
-- physical base backup of the whole cluster:
pg_basebackup -D /backup -Ft -z -P

Why it happens

pg_dump produces a logical, version-portable snapshot of one database — great for migrations and selective restores, but slow to restore at scale and not point-in-time. A physical base backup + WAL enables fast full-cluster restore and PITR.

This is a Pro lesson

Get every Learning Pathway and cookbook recipe — grounded in PostgreSQL source code, with diagnostics, fixes, and prevention for each topic.

Continue this lesson to learn:

  • How to fix it
  • Prevent it next time
  • Related & next steps
  • All 36 Learning Pathway lessons
  • 170+ cookbook recipes
  • Source-grounded diagnostics & fixes

Secure checkout Cancel anytime Source-grounded

Career Impact

This scenario builds production judgment and operational confidence under pressure.

Open Career Dashboard →

Keep going

Related & next steps

Was this helpful?

← All cookbook recipes