aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Eisentraut <peter_e@gmx.net>2015-06-13 21:45:56 -0400
committerPeter Eisentraut <peter_e@gmx.net>2015-06-13 21:45:56 -0400
commita85054181b3e60d44d896168127b7f7e204ea9f4 (patch)
treea5fa4dea9993716f74be46d740f879829186a259
parent340c74dfdfb91d521fbdb20e5601973266da3428 (diff)
downloadpostgresql-a85054181b3e60d44d896168127b7f7e204ea9f4.tar.gz
postgresql-a85054181b3e60d44d896168127b7f7e204ea9f4.zip
doc: Add note to pg_dump man page about pg_dumpall
suggested by Joshua Drake
-rw-r--r--doc/src/sgml/ref/pg_dump.sgml6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml
index c78f71d9a7a..7c28bd2876d 100644
--- a/doc/src/sgml/ref/pg_dump.sgml
+++ b/doc/src/sgml/ref/pg_dump.sgml
@@ -46,6 +46,12 @@ PostgreSQL documentation
</para>
<para>
+ <application>pg_dump</application> only dumps a single database. To backup
+ global objects that are common to all databases in a cluster, such as roles
+ and tablespaces, use <xref linkend="app-pg-dumpall">.
+ </para>
+
+ <para>
Dumps can be output in script or archive file formats. Script
dumps are plain-text files containing the SQL commands required
to reconstruct the database to the state it was in at the time it was