The man page does not clearly state that pg_dump will not dump things
like users or roles. It does mention briefly in the notes section that
pg_dumpall is needed for items that are set via SET but that isn't very
clear on the other items.
--
Command Prompt, Inc. - http://www.commandprompt.com/ 503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Announcing "I'm offended" is basically telling the world you can't
control your own emotions, so everyone else should do it for you.
diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml
index a6e7b08..4cb647c 100644
--- a/doc/src/sgml/ref/pg_dump.sgml
+++ b/doc/src/sgml/ref/pg_dump.sgml
@@ -45,6 +45,14 @@ PostgreSQL documentation
accessing the database (readers or writers).
</para>
+ <warning>
+ <para>
+ <xref linkend="app-pg-dumpall"> is required for a full backup as
+ <application>pg_dump</application> does not backup the required global
+ options such as user or roles.
+ </para>
+ </warning>
+
<para>
Dumps can be output in script or archive file formats. Script
dumps are plain-text files containing the SQL commands required
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
