From 42ffb83a38aecb6297435bc29b7441698851008f Mon Sep 17 00:00:00 2001 From: Laurenz Albe Date: Fri, 27 Feb 2026 23:18:09 +0100 Subject: [PATCH v2] pg_dumpall doc: add more clarity Add a sentence that describes the parts of a cluster's state that are *not* included in the output. In the spirit of added clarity, swap two sentences in the introductory paragraph. Without that, it is not clear what the "it" at the beginning of the second sentence is referring to. Also, add a reference to pg_restore, since not all output formats are restored with pg_dump. Author: Laurenz Albe Discussion: https://postgr.es/m/CAGJBphSX2oMPPu%3DVM4U8NP4%2BqffFH_483tFQCJ_s-mOcN3DLDw%40mail.gmail.com --- doc/src/sgml/ref/pg_dumpall.sgml | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/doc/src/sgml/ref/pg_dumpall.sgml b/doc/src/sgml/ref/pg_dumpall.sgml index 49e5c99b09e..c5a69d0c93d 100644 --- a/doc/src/sgml/ref/pg_dumpall.sgml +++ b/doc/src/sgml/ref/pg_dumpall.sgml @@ -36,14 +36,19 @@ PostgreSQL documentation pg_dumpall is a utility for writing out (dumping) all PostgreSQL databases - of a cluster into an SQL script file or an archive. The output contains - SQL commands that can be used as input to to restore the databases. It does this by + of a cluster into an SQL script file or an archive. It does this by calling for each database in the cluster. + The output contains SQL commands that can be used + as input to or + to restore the databases. pg_dumpall also dumps global objects that are common to all databases, namely database roles, tablespaces, and privilege grants for configuration parameters. (pg_dump does not save these objects.) + The only part of a database cluster's state that is not + included in the output of pg_dumpall are the + configuration files and database parameters changed with + . -- 2.53.0