11<!--
2- $Header: /cvsroot/pgsql/doc/src/sgml/backup.sgml,v 2.25 2003/03/18 00:02:11 momjian Exp $
2+ $Header: /cvsroot/pgsql/doc/src/sgml/backup.sgml,v 2.26 2003/03/24 14:32:50 petere Exp $
33-->
44<chapter id="backup">
55 <title>Backup and Restore</title>
@@ -110,7 +110,7 @@ psql <replaceable class="parameter">dbname</replaceable> < <replaceable class
110110 <application>psql</> (e.g., with <literal>createdb -T template0
111111 <replaceable class="parameter">dbname</></literal>).
112112 <application>psql</> supports similar options to <application>pg_dump</>
113- for controlling the database server location and the usernames . See
113+ for controlling the database server location and the username . See
114114 its reference page for more information.
115115 </para>
116116
@@ -135,7 +135,7 @@ psql <replaceable class="parameter">dbname</replaceable> < <replaceable class
135135 <para>
136136 The ability of <application>pg_dump</> and <application>psql</> to
137137 write to or read from pipes makes it possible to dump a database
138- directly from one server to another, for example
138+ directly from one server to another; for example:
139139<programlisting>
140140pg_dump -h <replaceable>host1</> <replaceable>dbname</> | psql -h <replaceable>host2</> <replaceable>dbname</>
141141</programlisting>
@@ -179,27 +179,19 @@ pg_dumpall > <replaceable>outfile</>
179179 <sect2 id="backup-dump-large">
180180 <title>Large Databases</title>
181181
182- <note>
183- <title>Acknowledgement</title>
184- <para>
185- Originally written by Hannu Krosing
186- (<email>hannu@trust.ee</email>) on 1999-06-19
187- </para>
188- </note>
189-
190182 <para>
191183 Since <productname>PostgreSQL</productname> allows tables larger
192184 than the maximum file size on your system, it can be problematic
193- to dumpthe table to a file, since the resulting file will likely
185+ to dumpsuch a table to a file, since the resulting file will likely
194186 be larger than the maximum size allowed by your system. As
195- <application>pg_dump</>writes to the standard output, you can
196- just use standard*nix tools to work around this possible problem.
187+ <application>pg_dump</>can write to the standard output, you can
188+ just use standardUnix tools to work around this possible problem.
197189 </para>
198190
199191 <formalpara>
200192 <title>Use compressed dumps.</title>
201193 <para>
202- Use your favorite compression program, for example
194+ You can use your favorite compression program, for example
203195 <application>gzip</application>.
204196
205197<programlisting>
@@ -222,9 +214,10 @@ cat <replaceable class="parameter">filename</replaceable>.gz | gunzip | psql <re
222214 </formalpara>
223215
224216 <formalpara>
225- <title>Use <application >split</>.</title>
217+ <title>Use <command >split</>.</title>
226218 <para>
227- This allows you to split the output into pieces that are
219+ The <command>split</command> command
220+ allows you to split the output into pieces that are
228221 acceptable in size to the underlying file system. For example, to
229222 make chunks of 1 megabyte:
230223
@@ -338,7 +331,7 @@ tar -cf backup.tar /usr/local/pgsql/data
338331
339332 <listitem>
340333 <para>
341- If you have dug into the details of the file system layout you
334+ If you have dug into the details of the file system layoutof the data you
342335 may be tempted to try to back up or restore only certain
343336 individual tables or databases from their respective files or
344337 directories. This will <emphasis>not</> work because the
@@ -348,7 +341,7 @@ tar -cf backup.tar /usr/local/pgsql/data
348341 all transactions. A table file is only usable with this
349342 information. Of course it is also impossible to restore only a
350343 table and the associated <filename>pg_clog</filename> data
351- because thatwill render all other tables in the database
344+ because thatwould render all other tables in the database
352345 cluster useless.
353346 </para>
354347 </listitem>
@@ -381,7 +374,7 @@ tar -cf backup.tar /usr/local/pgsql/data
381374 server, using <application>pg_dump</>. (There are checks in place
382375 that prevent you from doing the wrong thing, so no harm can be done
383376 by confusing these things.) The precise installation procedure is
384- not subject of this section, these details are in <xref linkend="installation">.
377+ not subject of this section; these details are in <xref linkend="installation">.
385378 </para>
386379
387380 <para>
@@ -393,7 +386,7 @@ tar -cf backup.tar /usr/local/pgsql/data
393386pg_dumpall -p 5432 | psql -d template1 -p 6543
394387</programlisting>
395388
396- to transfer your data, or use an intermediate file if you want.
389+ to transfer your data. Or use an intermediate file if you want.
397390 Then you can shut down the old server and start the new server at
398391 the port the old one was running at. You should make sure that the
399392 database is not updated after you run <application>pg_dumpall</>,
@@ -413,7 +406,7 @@ pg_dumpall -p 5432 | psql -d template1 -p 6543
413406pg_dumpall > backup
414407pg_ctl stop
415408mv /usr/local/pgsql /usr/local/pgsql.old
416- cd/usr/src /postgresql-&version;
409+ cd~ /postgresql-&version;
417410gmake install
418411initdb -D /usr/local/pgsql/data
419412postmaster -D /usr/local/pgsql/data