Commit636b868

committed

doc: Clarify under what circumstances pg_dump needs superuser access.

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

1 parent9b4d52f commit636b868Copy full SHA for 636b868

File tree

-2

lines changed

-2

lines changed

Lines changed: 7 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -47,8 +47,13 @@ pg_dump <replaceable class="parameter">dbname</replaceable> > <replaceable cl`
`47`	`47`	`that you can perform this backup procedure from any remote host that has`
`48`	`48`	`access to the database. But remember that <application>pg_dump</>`
`49`	`49`	`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>.)`
`52`	`57`	`</para>`
`53`	`58`
`54`	`59`	`<para>`

Comments

(0)