diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml index 83b72ad6b1..ea4501b923 100644 --- a/doc/src/sgml/backup.sgml +++ b/doc/src/sgml/backup.sgml @@ -1,4 +1,6 @@ - + Backup and Restore @@ -81,10 +83,12 @@ pg_dump dbname > - When your database schema relies on OIDs (for instances as foreign + When your database schema relies on OIDs (for instance as foreign keys) you must instruct pg_dump to dump the OIDs as well. To do this, use the command line - option. + option. Large objects are not dumped by default, either. + See pg_dump's command reference page if you use + large objects. @@ -115,7 +119,7 @@ psql dbname < psql to connect as each affected user in turn and then create the relevant objects. This way the original ownership is preserved. This also - means, however, that all these user must already exist, and + means, however, that all these users must already exist, and furthermore that you must be allowed to connect as each of them. It might therefore be necessary to temporarily relax the client authentication settings. @@ -123,8 +127,8 @@ psql dbname < The ability of pg_dump and psql to - write or read from pipes also make it possible to dump a database - directory from one server to another, for example + write to or read from pipes makes it possible to dump a database + directly from one server to another, for example pg_dump -h host1 dbname | psql -h host2 dbname