<!--

$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.71 2004/06/07 20:35:57 momjian Exp $

$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.72 2004/07/10 15:51:28 momjian Exp $

PostgreSQL documentation

-->

<term><option>--data-only</></term>

<listitem>

<para>

Dump only the data, not theschema (datadefinitions).

Dump only the data, not theobjectdefinitions (schema)

</para>

<para>

<para>

Output a <command>tar</command> archive suitable for input into

<application>pg_restore</application>. Using this archive format

allows reordering and/or exclusion ofschema elements

allows reordering and/or exclusion ofdatabase objects

at the time the database is restored. It is also possible to limit

which data is reloaded at restore time.

</para>

<para>

Output a custom archive suitable for input into

<application>pg_restore</application>. This is the most flexible

format in that it allows reordering ofdata load as well

asschema elements. This format is also compressed by default.

format in that it allows reordering ofloading data as well

asobject definitions. This format is also compressed by default.

</para>

</listitem>

</varlistentry>

ownership of objects to match the original database.

By default, <application>pg_dump</application> issues

<command>SET SESSION AUTHORIZATION</command>

statements to set ownership of createdschema elements.

statements to set ownership of createddatabase objects.

These statements

will fail when the script is run unless it is started by a superuser

(or the same user that owns all of the objects in the script).

<term><option>--schema-only</option></term>

<listitem>

<para>

Dump only theschema (datadefinitions),no data.

Dump only theobjectdefinitions (schema),not data.

</para>

</listitem>

</varlistentry>