pg_dump.sgml 23.6 KB
Newer Older
1
<!--
2
$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.50 2002/09/06 21:58:36 petere Exp $
3
PostgreSQL documentation
4 5 6
-->

<refentry id="APP-PGDUMP">
7
 <refmeta>
8
  <refentrytitle>pg_dump</refentrytitle>
9
  <manvolnum>1</manvolnum>
10 11
  <refmiscinfo>Application</refmiscinfo>
 </refmeta>
12

13
 <refnamediv>
14 15
  <refname>pg_dump</refname>

16
  <refpurpose>
17
   extract a <productname>PostgreSQL</productname> database into a script file or other archive file 
18 19
  </refpurpose>
 </refnamediv>
20

21
 <refsynopsisdiv>
22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38
  <cmdsynopsis>
   <command>pg_dump</command>
   <group> <arg>-a</arg> <arg>-s</arg> </group>
   <arg>-b</arg>
   <arg>-c</arg>
   <arg>-C</arg>
   <group> <arg>-d</arg> <arg>-D</arg> </group>
   <arg>-f <replaceable>file</replaceable></arg> 
   <arg>-F <replaceable>format</replaceable></arg>
   <arg>-i</arg>
   <arg>-o</arg>
   <arg>-O</arg>
   <arg>-R</arg>
   <arg>-S</arg>
   <arg>-t <replaceable>table</replaceable></arg>
   <arg>-v</arg>
   <arg>-x</arg>
39
   <arg>-X <replaceable>keyword</replaceable></arg>
40 41 42
   <arg>-Z <replaceable>0...9</replaceable></arg>
   <arg>-h <replaceable>host</replaceable></arg>
   <arg>-p <replaceable>port</replaceable></arg>
43 44
   <arg>-U <replaceable>username</replaceable></arg>
   <arg>-W</arg>
45
   <arg><replaceable>dbname</replaceable></arg>
46 47 48 49 50 51 52 53 54 55
  </cmdsynopsis>
 </refsynopsisdiv>


 <refsect1 id="pg-dump-description">
  <title>
   Description
  </title>

  <para>
56 57
   <command>pg_dump</command> is a utility for saving a
   <productname>PostgreSQL</productname> database into a script or an
Peter Eisentraut's avatar
Peter Eisentraut committed
58
   archive file.  The script files are in plain-text format and
59
   contain the SQL commands required to reconstruct the database to
60
   the state it was in at the time it was saved.  They can be used to
61 62
   reconstruct the database even on other machines and other
   architectures, with some modifications even on other RDBMS
Peter Eisentraut's avatar
Peter Eisentraut committed
63 64
   products.  Furthermore, there are alternative archive file formats that
   are meant to be
65 66 67 68 69
   used with <xref linkend="app-pgrestore"> to rebuild the database,
   and they also allow <command>pg_restore</command> 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.
70 71 72
  </para>

  <para>
73 74 75 76 77
   <command>pg_dump</command> will save the information necessary to
   re-generate all user-defined types, functions, tables, indexes,
   aggregates, and operators.  In addition, all the data is copied out
   in text format so that it can be readily copied in again, as well
   as imported into tools for editing.
78 79 80 81 82
  </para>

  <para>
   <command>pg_dump</command> 
   is useful for dumping out the contents of a database to move from one
Peter Eisentraut's avatar
Peter Eisentraut committed
83
   <productname>PostgreSQL</productname> installation to another.
84 85 86
  </para>

  <para>
87
   When used with one of the archive file formats and combined with
88 89
   <xref linkend="app-pgrestore">, <command>pg_dump</command> provides a
   flexible archival and 
90 91 92
   transfer mechanism. <command>pg_dump</command> can be used to
   backup an entire database, then <command>pg_restore</command> can
   be used to examine the archive and/or select which parts of the
93 94 95 96 97 98 99 100
   database are to be restored.
   The most flexible output file format is the <quote>custom</quote>
   format (<option>-Fc</option>). It allows for selection and
   reordering of all archived items, and is compressed by default. The
   <filename>tar</filename> format (<option>-Ft</option>) is not
   compressed and it is not possible to reorder data when loading, but
   it is otherwise quite flexible; moreover, it can be manipulated with
   other tools such as <filename>tar</filename>.
101 102 103 104 105 106 107 108 109 110 111 112 113
  </para>

  <para>
   While running <command>pg_dump</command>, one should examine the
   output for any warnings (printed on standard error), especially in
   light of the limitations listed below.
  </para>

  <para>
   <command>pg_dump</command> makes consistent backups even if the
   database is being used concurrently.  <command>pg_dump</command>
   does not block other users accessing the database (readers or
   writers).
114
  </para>
115
 </refsect1>
116

117 118
 <refsect1 id="pg-dump-options">
  <title>Options</title>
119

120 121
  <para>
   The following command-line options are used to control the output format.
122 123 124 125 126 127

    <variablelist>
     <varlistentry>
      <term><replaceable class="parameter">dbname</replaceable></term>
      <listitem>
       <para>
128 129 130 131
	Specifies the name of the database to be dumped.  If this is
	not specified, the environment variable
	<envar>PGDATABASE</envar> is used.  If that is not set, the
	user name specified for the connection is used.
132 133 134 135 136
       </para>
      </listitem>
     </varlistentry>

     <varlistentry>
137 138
      <term><option>-a</></term>
      <term><option>--data-only</></term>
139 140
      <listitem>
       <para>
141
	Dump only the data, not the schema (data definitions).
142
       </para>
143 144

       <para>
Peter Eisentraut's avatar
Peter Eisentraut committed
145
        This option is only meaningful for the plain-text format.  For
146 147 148
        the other formats, you may specify the option when you
        call <command>pg_restore</command>.
       </para>
149 150 151
      </listitem>
     </varlistentry>

152
     <varlistentry>
153 154
      <term><option>-b</></term>
      <term><option>--blobs</></term>
155 156
      <listitem>
       <para>
157
 	Include large objects in dump.
158 159 160 161 162
       </para>
      </listitem>
     </varlistentry>

     <varlistentry>
163 164
      <term><option>-c</option></term>
      <term><option>--clean</option></term>
165 166
      <listitem>
       <para>
167 168 169 170 171
        Output commands to clean (drop)
	database objects prior to (the commands for) creating them.
       </para>

       <para>
Peter Eisentraut's avatar
Peter Eisentraut committed
172
        This option is only meaningful for the plain-text format.  For
173 174
        the other formats, you may specify the option when you
        call <command>pg_restore</command>.
175 176 177 178 179
       </para>
      </listitem>
     </varlistentry>

     <varlistentry>
180 181
      <term><option>-C</></term>
      <term><option>--create</></term>
182 183
      <listitem>
       <para>
184 185 186 187 188 189 190
	Begin the output with a command to create the
	database itself and reconnect to the created database.  (With a
	script of this form, it doesn't matter which database you connect
	to before running the script.)
       </para>

       <para>
Peter Eisentraut's avatar
Peter Eisentraut committed
191
        This option is only meaningful for the plain-text format.  For
192 193
        the other formats, you may specify the option when you
        call <command>pg_restore</command>.
194 195 196 197
       </para>
      </listitem>
     </varlistentry>

198
     <varlistentry>
199 200
      <term><option>-d</option></term>
      <term><option>--inserts</option></term>
201 202
      <listitem>
       <para>
203
	Dump data as <command>INSERT</command> commands (rather
204 205 206
	than <command>COPY</command>). This will make restoration very
	slow, but it makes the archives more portable to other RDBMS
	packages.
207 208 209 210 211
       </para>
      </listitem>
     </varlistentry>

     <varlistentry>
212 213 214
      <term><option>-D</option></term>
      <term><option>--column-inserts</option></term>
      <term><option>--attribute-inserts</option></term>
215 216
      <listitem>
       <para>
217
	Dump data as <command>INSERT</command> commands with explicit
218 219 220
	column names (<literal>INSERT INTO
	<replaceable>table</replaceable>
	(<replaceable>column</replaceable>, ...) VALUES
221 222
	...</literal>).  This will make restoration very slow,
	but it is necessary if you desire to rearrange column ordering.
223 224 225
       </para>
      </listitem>
     </varlistentry>
226 227

     <varlistentry>
228 229
      <term><option>-f <replaceable class="parameter">file</replaceable></option></term>
      <term><option>--file=<replaceable class="parameter">file</replaceable></option></term>
230 231
      <listitem>
       <para>
232 233
	Send output to the specified file.  If this is omitted, the
	standard output is used.
234 235 236 237 238
       </para>
      </listitem>
     </varlistentry>

     <varlistentry>
239 240
      <term><option>-F <replaceable class="parameter">format</replaceable></option></term>
      <term><option>--format=<replaceable class="parameter">format</replaceable></option></term>
241 242
      <listitem>
       <para>
243 244
        Selects the format of the output.
	<replaceable>format</replaceable> can be one of the following:
245 246 247 248 249 250

       <variablelist>
        <varlistentry>
         <term>p</term>
         <listitem>
          <para>
Peter Eisentraut's avatar
Peter Eisentraut committed
251
           Output a plain-text <acronym>SQL</acronym> script file (default)
252 253 254 255 256 257 258 259
          </para>
         </listitem>
        </varlistentry>

        <varlistentry>
         <term>t</term>
         <listitem>
          <para>
Peter Eisentraut's avatar
Peter Eisentraut committed
260
         Output a <filename>tar</filename> archive suitable for input into 
261
         <command>pg_restore</command>. Using this archive format 
262 263 264 265 266 267 268 269 270 271 272
         allows reordering and/or exclusion of schema elements 
         at the time the database is restored. It is also possible to limit 
         which data is reloaded at restore time.
          </para>
         </listitem>
        </varlistentry>

        <varlistentry>
         <term>c</term>
         <listitem>
          <para>
Peter Eisentraut's avatar
Peter Eisentraut committed
273
         Output a custom archive suitable for input into 
274
         <command>pg_restore</command>. This is the most flexible 
275 276 277 278 279 280 281
         format in that it allows reordering of data load as well 
         as schema elements. This format is also compressed by default.
          </para>
         </listitem>
        </varlistentry>

       </variablelist>
282
       </para>
283 284 285

      </listitem>
     </varlistentry>
286

287
     <varlistentry>
288 289
      <term><option>-i</></term>
      <term><option>--ignore-version</></term>
290 291
      <listitem>
       <para>
292 293
        Ignore version mismatch between <command>pg_dump</command>
	and the database server.  Since <command>pg_dump</command>
294
	knows a great deal about system catalogs, any given version of
295
	<command>pg_dump</command> is only intended to work with
296 297
	the corresponding release of the database server.  Use this option
	if you need to override the version check (and if
298
	<command>pg_dump</command> then fails, don't
299 300 301 302 303
	say you weren't warned).
       </para>
      </listitem>
     </varlistentry>

304
     <varlistentry>
305 306
      <term><option>-o</></term>
      <term><option>--oids</></term>
307 308
      <listitem>
       <para>
309
	Dump object identifiers (<acronym>OID</acronym>s) for every
310
	table.  Use this option if your application references the OID
311 312
	columns in some way (e.g., in a foreign key constraint).
	Otherwise, this option should not be used.
313 314 315 316 317
       </para>
      </listitem>
     </varlistentry>

     <varlistentry>
318 319
      <term><option>-O</></term>
      <term><option>--no-owner</option></term>
320 321
      <listitem>
       <para>
322
        Do not output commands to set the
323 324 325 326 327 328 329 330 331 332 333 334
	object ownership to match the original database.  Typically,
	<command>pg_dump</command> issues
	(<command>psql</command>-specific) <command>\connect</command>
	statements to set ownership of schema elements.  See also
	under <option>-R</option> and <option>-X
	use-set-session-authorization</option>.  Note that
	<option>-O</option> does not prevent all reconnections to the
	database, only the ones that are exclusively used for
	ownership adjustments.
       </para>

       <para>
Peter Eisentraut's avatar
Peter Eisentraut committed
335
        This option is only meaningful for the plain-text format.  For
336
        the other formats, you may specify the option when you
337
        call <command>pg_restore</command>.
338 339 340 341 342
       </para>
      </listitem>
     </varlistentry>

     <varlistentry>
343 344
      <term><option>-R</option></term>
      <term><option>--no-reconnect</option></term>
345 346
      <listitem>
       <para>
347
	Prohibit <command>pg_dump</command>
348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364
        from outputting a script that would require reconnections to
        the database while being restored.  An average restoration
        script usually has to reconnect several times as different
        users to set the original ownerships of the objects.  This
        option is a rather blunt instrument because it makes
        <command>pg_dump</command> lose this ownership information,
        <emphasis>unless</emphasis> you use the <option>-X
        use-set-session-authorization</option> option.
       </para>

       <para>
        One possible reason why reconnections during restore might not
        be desired is if the access to the database requires manual
        interaction (e.g., passwords).
       </para>

       <para>
Peter Eisentraut's avatar
Peter Eisentraut committed
365
        This option is only meaningful for the plain-text format.  For
366
        the other formats, you may specify the option when you
367
        call <command>pg_restore</command>.
368 369 370 371
       </para>
      </listitem>
     </varlistentry>

372
     <varlistentry>
373 374
      <term><option>-s</option></term>
      <term><option>--schema-only</option></term>
375 376
      <listitem>
       <para>
377
	Dump only the schema (data definitions), no data.
378 379 380 381
       </para>
      </listitem>
     </varlistentry>

382
     <varlistentry>
383 384
      <term><option>-S <replaceable class="parameter">username</replaceable></option></term>
      <term><option>--superuser=<replaceable class="parameter">username</replaceable></option></term>
385 386
      <listitem>
       <para>
387 388 389 390 391
        Specify the superuser user name to use when disabling triggers.
	This is only relevant if <option>--disable-triggers</> is used.
	(Usually, it's better to specify
	<option>--use-set-session-authorization</>, and then start the
	resulting script as superuser.)
392 393 394 395 396
       </para>
      </listitem>
     </varlistentry>

     <varlistentry>
397 398
      <term><option>-t <replaceable class="parameter">table</replaceable></option></term>
      <term><option>--table=<replaceable class="parameter">table</replaceable></option></term>
399 400 401 402 403 404 405
      <listitem>
       <para>
	Dump data for <replaceable class="parameter">table</replaceable> only.
       </para>
      </listitem>
     </varlistentry>

406
     <varlistentry>
407 408
      <term><option>-v</></term>
      <term><option>--verbose</></term>
409 410
      <listitem>
       <para>
411 412 413
	Specifies verbose mode.  This will cause
	<application>pg_dump</application> to print progress messages
	to standard error.
414 415 416 417 418
       </para>
      </listitem>
     </varlistentry>

     <varlistentry>
419 420 421
      <term><option>-x</></term>
      <term><option>--no-privileges</></term>
      <term><option>--no-acl</></term>
422 423
      <listitem>
       <para>
424 425 426 427 428 429
	Prevent dumping of access privileges (grant/revoke commands).
       </para>
      </listitem>
     </varlistentry>

     <varlistentry>
430 431
      <term><option>-X use-set-session-authorization</></term>
      <term><option>--use-set-session-authorization</></term>
432 433
      <listitem>
       <para>
Peter Eisentraut's avatar
Peter Eisentraut committed
434
        Normally, if a (plain-text mode) script generated by
435 436 437 438 439
        <command>pg_dump</command> must alter the current database
        user (e.g., to set correct object ownerships), it uses the
        <xref linkend="app-psql"> <command>\connect</command> command.
        This command actually opens a new connection, which might
        require manual interaction (e.g., passwords).  If you use the
440
        <option>-X use-set-session-authorization</option> option, then
441
        <command>pg_dump</command> will instead output <xref
442
        linkend="sql-set-session-authorization" endterm="sql-set-session-authorization-title"> commands.  This has
443 444 445 446 447 448 449
        the same effect, but it requires that the user restoring the
        database from the generated script be a database superuser.
        This option effectively overrides the <option>-R</option>
        option.
       </para>

       <para>
450
        Since <xref linkend="sql-set-session-authorization" endterm="sql-set-session-authorization-title"> is a
451 452 453 454 455 456
        standard SQL command, whereas <command>\connect</command> only
        works in <xref linkend="app-psql">, this option also enhances
        the theoretical portability of the output script.
       </para>

       <para>
Peter Eisentraut's avatar
Peter Eisentraut committed
457
        This option is only meaningful for the plain-text format.  For
458
        the other formats, you may specify the option when you
459
        call <command>pg_restore</command>.
460 461 462
       </para>
      </listitem>
     </varlistentry>
463

464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493
     <varlistentry>
      <term><option>-X disable-triggers</></term>
      <term><option>--disable-triggers</></term>
      <listitem>
       <para>
        This option is only relevant when creating a data-only dump.
	It instructs <command>pg_dump</command> to include commands
	to temporarily disable triggers on the target tables while
	the data is reloaded.  Use this if you have referential
	integrity checks or other triggers on the tables that you
	do not want to invoke during data reload.
       </para>

       <para>
        Presently, the commands emitted for <option>--disable-triggers</>
	must be done as superuser.  So, you should also specify
	a superuser name with <option>-S</>, or preferably specify
	<option>--use-set-session-authorization</> and then be careful to
	start the resulting script as a superuser.  If you give neither
	option, the entire script must be run as superuser.
       </para>

       <para>
        This option is only meaningful for the plain-text format.  For
        the other formats, you may specify the option when you
        call <command>pg_restore</command>.
       </para>
      </listitem>
     </varlistentry>

494
     <varlistentry>
495 496
      <term><option>-Z <replaceable class="parameter">0..9</replaceable></option></term>
      <term><option>--compress=<replaceable class="parameter">0..9</replaceable></option></term>
497 498 499 500 501 502 503
      <listitem>
       <para>
	Specify the compression level to use in archive formats that support 
      compression (currently only the custom archive format supports compression).
       </para>
      </listitem>
     </varlistentry>
504 505
    </variablelist>
   </para>
506

507
   <para>
508
    The following command-line options control the database connection parameters.
509 510 511

    <variablelist>
     <varlistentry>
512 513
      <term><option>-h <replaceable class="parameter">host</replaceable></option></term>
      <term><option>--host=<replaceable class="parameter">host</replaceable></option></term>
514 515
      <listitem>
       <para>
516
	Specifies the host name of the machine on which the 
Peter Eisentraut's avatar
Peter Eisentraut committed
517
	server
518
	is running.  If host begins with a slash, it is used 
519
	as the directory for the Unix domain socket.
520 521 522 523 524
       </para>
      </listitem>
     </varlistentry>

     <varlistentry>
525 526
      <term><option>-p <replaceable class="parameter">port</replaceable></option></term>
      <term><option>--port=<replaceable class="parameter">port</replaceable></option></term>
527 528 529
      <listitem>
       <para>
	Specifies the Internet TCP/IP port or local Unix domain socket file 
Peter Eisentraut's avatar
Peter Eisentraut committed
530
	extension on which the server
531 532 533 534 535 536 537 538
	is listening for connections.  The port number defaults to 5432,
	or the value of the <envar>PGPORT</envar>
	environment variable (if set).
       </para>
      </listitem>
     </varlistentry>

     <varlistentry>
539
      <term><option>-U <replaceable>username</replaceable></option></term>
540 541
      <listitem>
       <para>
542
        Connect as the given user
543 544 545 546 547
       </para>
      </listitem>
     </varlistentry>

     <varlistentry>
548
      <term><option>-W</option></term>
549 550 551 552
      <listitem>
       <para>
        Force a password prompt.  This should happen automatically if
        the server requires password authentication.
553 554 555 556 557 558
       </para>
      </listitem>
     </varlistentry>
    </variablelist>
   </para>

559 560 561
  <para>
   Long option forms are only available on some platforms.
  </para>
562
 </refsect1>
563

564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582
 <refsect1>
  <title>Environment</title>

  <variablelist>
   <varlistentry>
    <term><envar>PGDATABASE</envar></term>
    <term><envar>PGHOST</envar></term>
    <term><envar>PGPORT</envar></term>
    <term><envar>PGUSER</envar></term>

    <listitem>
     <para>
      Default connection parameters
     </para>
    </listitem>
   </varlistentry>
  </variablelist>
 </refsect1>

583 584 585 586 587 588 589 590 591
 <refsect1 id="app-pgdump-diagnostics">
  <title>Diagnostics</title>

  <msgset>
   <msgentry>
    <msg>
     <msgmain>
      <msgtext>
<screen><computeroutput>
592
Connection to database 'template1' failed.
593 594 595
connectDBStart() -- connect() failed: No such file or directory
        Is the postmaster running locally
        and accepting connections on Unix socket '/tmp/.s.PGSQL.5432'?
596 597 598 599 600 601
</computeroutput></screen>
      </msgtext>
     </msgmain> 
    </msg>

    <msgexplan>
602
       <para>
603 604
	<command>pg_dump</command> could not attach to the 
	<command>postmaster</command> 
605
	process on the specified host and port.  If you see this message,
606
	ensure that the <command>postmaster</command> 
607
	is running on the proper host and that you have specified the proper
608
	port.
609
       </para>
610 611 612 613
    </msgexplan>
   </msgentry>

  </msgset>
614 615

   <note>
616
    <para>
617
     <command>pg_dump</command> internally executes
618
     <command>SELECT</command> statements. If you have problems running
619
     <command>pg_dump</command>,
620
     make sure you are able to select information from the database using, for
621
     example, <xref linkend="app-psql">.
622
    </para>
623 624 625
   </note>
 </refsect1>

626 627 628

 <refsect1 id="pg-dump-notes">
  <title>Notes</title>
629 630 631 632 633 634 635 636 637 638 639 640 641

  <para>
   If your installation has any local additions to the template1 database,
   be careful to restore the output of <command>pg_dump</command> into a
   truly empty database; otherwise you are likely to get errors due to
   duplicate definitions of the added objects.  To make an empty database
   without any local additions, copy from template0 not template1,
   for example:
<programlisting>
CREATE DATABASE foo WITH TEMPLATE = template0;
</programlisting>
  </para>

642
  <para>
643
   <command>pg_dump</command> has a few limitations:
644 645 646 647

   <itemizedlist>
    <listitem>
     <para>
648
      When dumping a single table or as plain text, <command>pg_dump</command> 
649
      does not handle large objects. Large objects must be dumped in their
650
      entirety using one of the binary archive formats.
651 652
     </para>
    </listitem>
653 654 655

    <listitem>
     <para>
656
      When doing a data only dump, <command>pg_dump</command> emits queries
657
      to disable triggers on user tables before inserting the data and queries to
Bruce Momjian's avatar
Bruce Momjian committed
658
      re-enable them after the data has been inserted.  If the restore is stopped
659 660 661 662
      in the middle, the system catalogs may be left in the wrong state.
     </para>
    </listitem>

663 664
   </itemizedlist>
  </para>
665 666 667 668 669 670 671 672 673

  <para>
   Members of tar archives are limited to a size less than 8 GB.
   (This is an inherent limitation of the tar file format.)  Therefore
   this format cannot be used if the textual representation of a table
   exceeds that size.  The total size of a tar archive and any of the
   other output formats is not limited, except possibly by the
   operating system.
  </para>
674 675
 </refsect1>

676 677
 <refsect1 id="pg-dump-examples">
  <title>Examples</title>
678

679 680 681 682 683
  <para>
   To dump a database:
<screen>
<prompt>$</prompt> <userinput>pg_dump mydb &gt; db.out</userinput>
</screen>
684 685 686 687
  </para>

  <para>
   To reload this database:
688 689 690
<screen>
<prompt>$</prompt> <userinput>psql -d database -f db.out</userinput>
</screen>
691
  </para>
692 693

  <para>
694 695
   To dump a database called <literal>mydb</> that contains
   large objects to a <filename>tar</filename> file:
696

697 698 699
<screen>
<prompt>$</prompt> <userinput>pg_dump -Ft -b mydb &gt; db.tar</userinput>
</screen>
700 701 702
  </para>

  <para>
703 704
   To reload this database (with large objects) to an
   existing database called <literal>newdb</>:
705

706 707 708
<screen>
<prompt>$</prompt> <userinput>pg_restore -d newdb db.tar</userinput>
</screen>
709 710
  </para>

711
 </refsect1>
712

713 714 715 716 717
 <refsect1>
  <title>History</title>

  <para>
   The <command>pg_dump</command> utility first appeared in
718
   <application>Postgres95</application> release <literal>0.02</literal>.  The
719
   non-plain-text output formats were introduced in
720
   <application>PostgreSQL</application> release <literal>7.1</literal>.
721 722 723
  </para>
 </refsect1>

724 725 726 727 728 729 730 731 732 733 734
 <refsect1>
  <title>See Also</title>

  <simplelist type="inline">
   <member><xref linkend="app-pg-dumpall"></member>
   <member><xref linkend="app-pgrestore"></member>
   <member><xref linkend="app-psql"></member>
   <member><citetitle>PostgreSQL Administrator's Guide</citetitle></member>
  </simplelist>
 </refsect1>

735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752
</refentry>

<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:nil
sgml-shorttag:t
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:1
sgml-indent-data:t
sgml-parent-document:nil
sgml-default-dtd-file:"../reference.ced"
sgml-exposed-tags:nil
sgml-local-catalogs:"/usr/lib/sgml/catalog"
sgml-local-ecat-files:nil
End:
-->