aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2006-05-06 23:25:37 +0000
committerBruce Momjian <bruce@momjian.us>2006-05-06 23:25:37 +0000
commitd9d2d91544ebe9cfae6c677828cbad12f5291150 (patch)
treec7632f4f269d1aea26f45e83bc24d34c17a16ecb
parentbcf860b7f30aeed179297fc6ea3985f68f91b0e8 (diff)
downloadpostgresql-d9d2d91544ebe9cfae6c677828cbad12f5291150.tar.gz
postgresql-d9d2d91544ebe9cfae6c677828cbad12f5291150.zip
Recommend more clearly custom pg_dump format over tar, buy showing
custom format examples first.
-rw-r--r--doc/src/sgml/ref/pg_dump.sgml34
1 files changed, 17 insertions, 17 deletions
diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml
index b29fe248dcf..9e076a43083 100644
--- a/doc/src/sgml/ref/pg_dump.sgml
+++ b/doc/src/sgml/ref/pg_dump.sgml
@@ -1,5 +1,5 @@
<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.83 2006/04/15 18:11:16 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.84 2006/05/06 23:25:37 momjian Exp $
PostgreSQL documentation
-->
@@ -244,28 +244,28 @@ PostgreSQL documentation
</varlistentry>
<varlistentry>
- <term><literal>t</></term>
- <term><literal>tar</></term>
+ <term><literal>c</></term>
+ <term><literal>custom</></term>
<listitem>
<para>
- Output a <command>tar</command> archive suitable for input into
- <application>pg_restore</application>. 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
+ <application>pg_restore</application>. 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.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><literal>c</></term>
- <term><literal>custom</></term>
+ <term><literal>t</></term>
+ <term><literal>tar</></term>
<listitem>
<para>
- Output a custom archive suitable for input into
- <application>pg_restore</application>. 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 <command>tar</command> archive suitable for input into
+ <application>pg_restore</application>. 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.
</para>
</listitem>
</varlistentry>
@@ -665,11 +665,11 @@ CREATE DATABASE foo WITH TEMPLATE template0;
</para>
<para>
- To dump a database called <literal>mydb</> to a <filename>tar</filename>
+ To dump a database called <literal>mydb</> to a file in custom format:
file:
<screen>
-<prompt>$</prompt> <userinput>pg_dump -Ft mydb &gt; db.tar</userinput>
+<prompt>$</prompt> <userinput>pg_dump -Fc mydb &gt; db.out</userinput>
</screen>
</para>
@@ -677,7 +677,7 @@ CREATE DATABASE foo WITH TEMPLATE template0;
To reload this dump into an existing database called <literal>newdb</>:
<screen>
-<prompt>$</prompt> <userinput>pg_restore -d newdb db.tar</userinput>
+<prompt>$</prompt> <userinput>pg_restore -d newdb db.out</userinput>
</screen>
</para>