Fix markup.
This commit is contained in:
parent
7fdaf78ed0
commit
2736ad31dc
|
@ -1,4 +1,4 @@
|
||||||
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/backup.sgml,v 2.5 2001/03/13 14:08:18 pjw Exp $ -->
|
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/backup.sgml,v 2.6 2001/03/14 22:20:02 petere Exp $ -->
|
||||||
<chapter id="backup">
|
<chapter id="backup">
|
||||||
<title>Backup and Restore</title>
|
<title>Backup and Restore</title>
|
||||||
|
|
||||||
|
@ -103,7 +103,7 @@ psql <replaceable class="parameter">dbname</replaceable> < <replaceable class
|
||||||
class="parameter">dbname</replaceable> will not be created by this
|
class="parameter">dbname</replaceable> will not be created by this
|
||||||
command, you must create it yourself from template0 before executing
|
command, you must create it yourself from template0 before executing
|
||||||
<application>psql</> (e.g., with <userinput>createdb -t template0
|
<application>psql</> (e.g., with <userinput>createdb -t template0
|
||||||
<replaceableclass="parameter">dbname</></userinput>).
|
<replaceable class="parameter">dbname</></userinput>).
|
||||||
<application>psql</> supports similar options to <application>pg_dump</>
|
<application>psql</> supports similar options to <application>pg_dump</>
|
||||||
for controlling the database server location and the user names. See
|
for controlling the database server location and the user names. See
|
||||||
its reference page for more information.
|
its reference page for more information.
|
||||||
|
@ -135,7 +135,7 @@ pg_dump -h <replaceable>host1</> <replaceable>dbname</> | psql -h <replaceable>h
|
||||||
<important>
|
<important>
|
||||||
<para>
|
<para>
|
||||||
The dumps produced by pg_dump are relative to template0. This means
|
The dumps produced by pg_dump are relative to template0. This means
|
||||||
that any languages, procedure etc added to template1 will also be
|
that any languages, procedures, etc. added to template1 will also be
|
||||||
dumped by <application>pg_dump</>. As a result, when restoring, if
|
dumped by <application>pg_dump</>. As a result, when restoring, if
|
||||||
you are using a customized template1, you must create the empty
|
you are using a customized template1, you must create the empty
|
||||||
database from template0, as in the example above.
|
database from template0, as in the example above.
|
||||||
|
@ -293,7 +293,7 @@ pg_dump -Fc <replaceable class="parameter">dbname</replaceable> > <replaceable c
|
||||||
<para>
|
<para>
|
||||||
For reasons of backward compatibility, <application>pg_dump</> does
|
For reasons of backward compatibility, <application>pg_dump</> does
|
||||||
not dump large objects by default. To dump large objects you must use
|
not dump large objects by default. To dump large objects you must use
|
||||||
either custom or TAR output format, and use the -B option in
|
either the custom or the TAR output format, and use the -B option in
|
||||||
<application>pg_dump</>. See the reference pages for details.
|
<application>pg_dump</>. See the reference pages for details.
|
||||||
The directory <filename>contrib/pg_dumplo</> of the
|
The directory <filename>contrib/pg_dumplo</> of the
|
||||||
<productname>Postgres</> source tree also contains a program that can
|
<productname>Postgres</> source tree also contains a program that can
|
||||||
|
|
Loading…
Reference in New Issue