|
1 | 1 | <!-- |
2 | | -$Header: /cvsroot/pgsql/doc/src/sgml/backup.sgml,v 2.26 2003/03/24 14:32:50 petere Exp $ |
| 2 | +$Header: /cvsroot/pgsql/doc/src/sgml/backup.sgml,v 2.27 2003/08/01 01:01:52 tgl Exp $ |
3 | 3 | --> |
4 | 4 | <chapter id="backup"> |
5 | 5 | <title>Backup and Restore</title> |
@@ -163,16 +163,21 @@ pg_dump -h <replaceable>host1</> <replaceable>dbname</> | psql -h <replaceable>h |
163 | 163 | up an entire database cluster. For this reason the |
164 | 164 | <application>pg_dumpall</> program is provided. |
165 | 165 | <application>pg_dumpall</> backs up each database in a given |
166 | | - cluster and alsomakes sure that the state of global data such as |
167 | | - users and groups is preserved. The call sequence for |
| 166 | + cluster, and alsopreserves cluster-wide data such as |
| 167 | + users and groups. The call sequence for |
168 | 168 | <application>pg_dumpall</> is simply |
169 | 169 | <synopsis> |
170 | 170 | pg_dumpall > <replaceable>outfile</> |
171 | 171 | </synopsis> |
172 | | - The resulting dumps can be restored with <application>psql</> as |
173 | | - described above. But in this case it is definitely necessary that |
174 | | - you have database superuser access, as that is required to restore |
175 | | - the user and group information. |
| 172 | + The resulting dump can be restored with <application>psql</>: |
| 173 | +<synopsis> |
| 174 | +psql template1 < <replaceable class="parameter">infile</replaceable> |
| 175 | +</synopsis> |
| 176 | + (Actually, you can specify any existing database name to start from, |
| 177 | + but if you are reloading in an empty cluster then <literal>template1</> |
| 178 | + is the only available choice.) It is always necessary to have |
| 179 | + database superuser access when restoring a <application>pg_dumpall</> |
| 180 | + dump, as that is required to restore the user and group information. |
176 | 181 | </para> |
177 | 182 | </sect2> |
178 | 183 |
|
@@ -260,7 +265,7 @@ pg_dump -Fc <replaceable class="parameter">dbname</replaceable> > <replaceable c |
260 | 265 | <para> |
261 | 266 | <application>pg_dump</> (and by implication |
262 | 267 | <application>pg_dumpall</>) has a few limitations which stem from |
263 | | - the difficultyto reconstruct certain information from the system |
| 268 | + the difficultyof reconstructing certain information from the system |
264 | 269 | catalogs. |
265 | 270 | </para> |
266 | 271 |
|
|