From: Peter Eisentraut Date: Wed, 14 Mar 2001 22:20:02 +0000 (+0000) Subject: Fix markup. X-Git-Tag: REL7_1~183 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=2736ad31dc68bc3294bb6c9d1a56c424d62bf2b5;p=postgresql Fix markup. --- diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml index 49e139cc6e..89ad624674 100644 --- a/doc/src/sgml/backup.sgml +++ b/doc/src/sgml/backup.sgml @@ -1,4 +1,4 @@ - + Backup and Restore @@ -103,7 +103,7 @@ psql dbname < dbname will not be created by this command, you must create it yourself from template0 before executing psql (e.g., with createdb -t template0 - dbname). + dbname). psql supports similar options to pg_dump for controlling the database server location and the user names. See its reference page for more information. @@ -135,7 +135,7 @@ pg_dump -h host1 dbname | psql -h h 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 pg_dump. As a result, when restoring, if you are using a customized template1, you must create the empty database from template0, as in the example above. @@ -293,7 +293,7 @@ pg_dump -Fc dbname > For reasons of backward compatibility, pg_dump does 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 pg_dump. See the reference pages for details. The directory contrib/pg_dumplo of the Postgres source tree also contains a program that can