diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml
index b29fe248dcf4e1b6854aaa263a5ccf7cb4ff2c87..9e076a43083050a016b532b956e09afd4f70f5a8 100644
--- a/doc/src/sgml/ref/pg_dump.sgml
+++ b/doc/src/sgml/ref/pg_dump.sgml
@@ -1,5 +1,5 @@
@@ -244,28 +244,28 @@ PostgreSQL documentation
- t>
- tar>
+ c>
+ custom>
- Output a tar archive suitable for input into
- pg_restore. Using this archive format
- allows reordering and/or exclusion of database objects
- at the time the database is restored. It is also possible to limit
- which data is reloaded at restore time.
+ Output a custom archive suitable for input into
+ pg_restore. This is the most flexible
+ format in that it allows reordering of loading data as well
+ as object definitions. This format is also compressed by default.
- c>
- custom>
+ t>
+ tar>
- Output a custom archive suitable for input into
- pg_restore. This is the most flexible
- format in that it allows reordering of loading data as well
- as object definitions. This format is also compressed by default.
+ Output a tar archive suitable for input into
+ pg_restore. Using this archive format
+ allows reordering and/or exclusion of database objects
+ at the time the database is restored. It is also possible to limit
+ which data is reloaded at restore time.
@@ -665,11 +665,11 @@ CREATE DATABASE foo WITH TEMPLATE template0;
- To dump a database called mydb> to a tar
+ To dump a database called mydb> to a file in custom format:
file:
-$ pg_dump -Ft mydb > db.tar
+$ pg_dump -Fc mydb > db.out
@@ -677,7 +677,7 @@ CREATE DATABASE foo WITH TEMPLATE template0;
To reload this dump into an existing database called newdb>:
-$ pg_restore -d newdb db.tar
+$ pg_restore -d newdb db.out