|
1 | 1 | <!-- |
2 | | -$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.83 2006/04/15 18:11:16 momjian Exp $ |
| 2 | +$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.84 2006/05/06 23:25:37 momjian Exp $ |
3 | 3 | PostgreSQL documentation |
4 | 4 | --> |
5 | 5 |
|
@@ -244,28 +244,28 @@ PostgreSQL documentation |
244 | 244 | </varlistentry> |
245 | 245 |
|
246 | 246 | <varlistentry> |
247 | | - <term><literal>t</></term> |
248 | | - <term><literal>tar</></term> |
| 247 | + <term><literal>c</></term> |
| 248 | + <term><literal>custom</></term> |
249 | 249 | <listitem> |
250 | 250 | <para> |
251 | | - Output a <command>tar</command> archive suitable for input into |
252 | | - <application>pg_restore</application>. Using this archive format |
253 | | - allows reordering and/or exclusion of database objects |
254 | | - at the time the database is restored. It is also possible to limit |
255 | | - which data is reloaded at restore time. |
| 251 | + Output a custom archive suitable for input into |
| 252 | + <application>pg_restore</application>. This is the most flexible |
| 253 | + format in that it allows reordering of loading data as well |
| 254 | + as object definitions. This format is also compressed by default. |
256 | 255 | </para> |
257 | 256 | </listitem> |
258 | 257 | </varlistentry> |
259 | 258 |
|
260 | 259 | <varlistentry> |
261 | | - <term><literal>c</></term> |
262 | | - <term><literal>custom</></term> |
| 260 | + <term><literal>t</></term> |
| 261 | + <term><literal>tar</></term> |
263 | 262 | <listitem> |
264 | 263 | <para> |
265 | | - Output a custom archive suitable for input into |
266 | | - <application>pg_restore</application>. This is the most flexible |
267 | | - format in that it allows reordering of loading data as well |
268 | | - as object definitions. This format is also compressed by default. |
| 264 | + Output a <command>tar</command> archive suitable for input into |
| 265 | + <application>pg_restore</application>. Using this archive format |
| 266 | + allows reordering and/or exclusion of database objects |
| 267 | + at the time the database is restored. It is also possible to limit |
| 268 | + which data is reloaded at restore time. |
269 | 269 | </para> |
270 | 270 | </listitem> |
271 | 271 | </varlistentry> |
@@ -665,19 +665,19 @@ CREATE DATABASE foo WITH TEMPLATE template0; |
665 | 665 | </para> |
666 | 666 |
|
667 | 667 | <para> |
668 | | - To dump a database called <literal>mydb</> to a<filename>tar</filename> |
| 668 | + To dump a database called <literal>mydb</> to afile in custom format: |
669 | 669 | file: |
670 | 670 |
|
671 | 671 | <screen> |
672 | | -<prompt>$</prompt> <userinput>pg_dump -Ft mydb > db.tar</userinput> |
| 672 | +<prompt>$</prompt> <userinput>pg_dump -Fc mydb > db.out</userinput> |
673 | 673 | </screen> |
674 | 674 | </para> |
675 | 675 |
|
676 | 676 | <para> |
677 | 677 | To reload this dump into an existing database called <literal>newdb</>: |
678 | 678 |
|
679 | 679 | <screen> |
680 | | -<prompt>$</prompt> <userinput>pg_restore -d newdb db.tar</userinput> |
| 680 | +<prompt>$</prompt> <userinput>pg_restore -d newdb db.out</userinput> |
681 | 681 | </screen> |
682 | 682 | </para> |
683 | 683 |
|
|