Differences between current version and predecessor to the previous major change of pg_dump(1).
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 4 | Last edited on Tuesday, June 4, 2002 12:22:41 am | by perry | |
| Older page: | version 3 | Last edited on Tuesday, June 4, 2002 12:22:41 am | by perry | Revert |
@@ -35,9 +35,9 @@
it was saved. They can be used to reconstruct the database
even on other machines and other architectures, with some
modifications even on other RDBMS products. Furthermore,
there are alternative archive file formats that are meant to
-be used with __
pg_restore__
(1) to rebuild the database,
+be used with pg_restore(1) to rebuild the database,
and they also allow __pg_restore__ to be selective about
what is restored, or even to reorder the items prior to
being restored. The archive files are also designed to be
portable across architectures.
@@ -56,9 +56,9 @@
another.
When used with one of the archive file formats and combined
-with __
pg_restore__
(1), __pg_dump__ provides a
+with pg_restore(1), __pg_dump__ provides a
flexible archival and transfer mechanism. __pg_dump__ can
be used to backup an entire database, then __pg_restore__
can be used to examine the archive and/or select which parts
of the database are to be restored. The most flexible output
@@ -531,7 +531,7 @@
7.1.
!!SEE ALSO
-__
pg_dumpall__
(1), __pg_restore__(1), psql(1),
+pg_dumpall(1), __pg_restore__(1), psql(1),
''PostgreSQL Administrator's Guide''
----
