From: Robert Haas <rhaas@postgresql.org>
Date: Fri, 8 Nov 2013 20:08:11 +0000 (-0500)
Subject: doc: Clarify under what circumstances pg_dump needs superuser access.
X-Git-Tag: REL9_4_BETA1~967
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=636b868f17a6d38c0f9e099ea8f389a555403f9e;p=postgresql

doc: Clarify under what circumstances pg_dump needs superuser access.

Inspired by, but different from, a patch from Ivan Lezhnjov IV
---

diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index ccb76d8af0..54681a0ba0 100644
--- a/doc/src/sgml/backup.sgml
+++ b/doc/src/sgml/backup.sgml
@@ -47,8 +47,13 @@ pg_dump <replaceable class="parameter">dbname</replaceable> &gt; <replaceable cl
    that you can perform this backup procedure from any remote host that has
    access to the database. But remember that <application>pg_dump</>
    does not operate with special permissions. In particular, it must
-   have read access to all tables that you want to back up, so in
-   practice you almost always have to run it as a database superuser.
+   have read access to all tables that you want to back up, so in order
+   to back up the entire database you almost always have to run it as a
+   database superuser.  (If you do not sufficient privileges to back up the
+   entire database, you can still back up portions of the database to which
+   you do have access using options such as
+   <option>-n <replaceable>schema</replaceable></option>
+   or <option>-t <replaceable>table</replaceable></option>.)
   </para>
 
   <para>