https://www.postgresscripts.com/tags/pg_dumpall/Recent content in Pg_dumpall on Postgres ScriptsHugo -- gohugo.ioenPostgresScripts.comTue, 09 Jun 2026 00:00:00 +0000https://www.postgresscripts.com/post/backup-all-postgresql-databases-with-pg-dumpall/Tue, 09 Jun 2026 00:00:00 +0000https://www.postgresscripts.com/post/backup-all-postgresql-databases-with-pg-dumpall/ <h2 id="back-up-all-postgresql-databases-with-pg_dumpall">Back Up All PostgreSQL Databases with pg_dumpall</h2> <p>Before a major-version upgrade or a disaster-recovery rehearsal, a DBA needs a single artifact that captures the whole cluster: every database, plus the global objects that live outside any one database. <code>pg_dumpall</code> produces exactly that — one plain-SQL script that recreates all databases together with the roles, tablespaces, and grants that <code>pg_dump</code> on its own leaves behind.</p> <script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-1012089347386563" crossorigin="anonymous"></script> <ins class="adsbygoogle" style="display:block" data-ad-client="ca-pub-1012089347386563" data-ad-slot="7945792173" data-ad-format="auto" data-full-width-responsive="true"></ins> <script> (adsbygoogle = window.adsbygoogle || []).push({}); </script> <h2 id="purpose-and-overview">Purpose and Overview</h2> <p><code>pg_dump</code> backs up a single database. It does a thorough job inside that database, but it does not capture cluster-wide objects. Roles (users and groups), role memberships, tablespace definitions, and the privileges attached to them are stored once per cluster, not once per database. Restore a <code>pg_dump</code> file into a fresh server and the owners and grant statements refer to roles that do not exist yet.</p>