Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 636b868

Browse files
committed
doc: Clarify under what circumstances pg_dump needs superuser access.
Inspired by, but different from, a patch from Ivan Lezhnjov IV
1 parent 9b4d52f commit 636b868

File tree

1 file changed

+7
-2
lines changed

1 file changed

+7
-2
lines changed

doc/src/sgml/backup.sgml

+7-2
Original file line numberDiff line numberDiff line change
@@ -47,8 +47,13 @@ pg_dump <replaceable class="parameter">dbname</replaceable> &gt; <replaceable cl
4747
that you can perform this backup procedure from any remote host that has
4848
access to the database. But remember that <application>pg_dump</>
4949
does not operate with special permissions. In particular, it must
50-
have read access to all tables that you want to back up, so in
51-
practice you almost always have to run it as a database superuser.
50+
have read access to all tables that you want to back up, so in order
51+
to back up the entire database you almost always have to run it as a
52+
database superuser. (If you do not sufficient privileges to back up the
53+
entire database, you can still back up portions of the database to which
54+
you do have access using options such as
55+
<option>-n <replaceable>schema</replaceable></option>
56+
or <option>-t <replaceable>table</replaceable></option>.)
5257
</para>
5358

5459
<para>

0 commit comments

Comments
 (0)