|
1 |
| -<!-- $Header: /cvsroot/pgsql/doc/src/sgml/backup.sgml,v 2.7 2001/03/19 16:19:26 petere Exp $ --> |
| 1 | +<!-- $Header: /cvsroot/pgsql/doc/src/sgml/backup.sgml,v 2.8 2001/05/17 21:12:48 petere Exp $ --> |
2 | 2 | <chapter id="backup">
|
3 | 3 | <title>Backup and Restore</title>
|
4 | 4 |
|
@@ -61,11 +61,10 @@ pg_dump <replaceable class="parameter">dbname</replaceable> > <replaceable cl
|
61 | 61 | As any other <productname>Postgres</> client application,
|
62 | 62 | <application>pg_dump</> will by default connect with the database
|
63 | 63 | user name that is equal to the current Unix user name. To override
|
64 |
| - this, either specify the <option>-u</option> option to force a prompt for |
65 |
| - the user name, or set the environment variable |
66 |
| - <envar>PGUSER</envar>. Remember that <application>pg_dump</> |
67 |
| - connections are subject to the normal client authentication |
68 |
| - mechanisms (which are described in <xref |
| 64 | + this, either specify the <option>-U</option> option or set the |
| 65 | + environment variable <envar>PGUSER</envar>. Remember that |
| 66 | + <application>pg_dump</> connections are subject to the normal |
| 67 | + client authentication mechanisms (which are described in <xref |
69 | 68 | linkend="client-authentication">).
|
70 | 69 | </para>
|
71 | 70 |
|
@@ -163,20 +162,6 @@ pg_dumpall > <replaceable>outfile</>
|
163 | 162 | you have database superuser access, as that is required to restore
|
164 | 163 | the user and group information.
|
165 | 164 | </para>
|
166 |
| - |
167 |
| - <para> |
168 |
| - <application>pg_dumpall</application> has one little flaw: It is |
169 |
| - not prepared for interactively authenticating to each database it |
170 |
| - dumps. If you are using password authentication then you need to |
171 |
| - set it the environment variable <envar>PGPASSWORD</envar> to |
172 |
| - communicate the password the the underlying calls to |
173 |
| - <application>pg_dump</>. More severely, if you have different |
174 |
| - passwords set up for each database, then |
175 |
| - <application>pg_dumpall</> will fail. You can either choose a |
176 |
| - different authentication mechanism for the purposes of backup or |
177 |
| - adjust the <filename>pg_dumpall</filename> shell script to your |
178 |
| - needs. |
179 |
| - </para> |
180 | 165 | </sect2>
|
181 | 166 |
|
182 | 167 | <sect2 id="backup-dump-large">
|
|
0 commit comments