From a85054181b3e60d44d896168127b7f7e204ea9f4 Mon Sep 17 00:00:00 2001
From: Peter Eisentraut <peter_e@gmx.net>
Date: Sat, 13 Jun 2015 21:45:56 -0400
Subject: [PATCH] doc: Add note to pg_dump man page about pg_dumpall

suggested by Joshua Drake
---
 doc/src/sgml/ref/pg_dump.sgml | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml
index c78f71d9a7..7c28bd2876 100644
--- a/doc/src/sgml/ref/pg_dump.sgml
+++ b/doc/src/sgml/ref/pg_dump.sgml
@@ -45,6 +45,12 @@ PostgreSQL documentation
    accessing the database (readers or writers).
   </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