1999-07-22 17:09:15 +02:00
|
|
|
<!--
|
2010-09-20 22:08:53 +02:00
|
|
|
doc/src/sgml/ref/pg_dump.sgml
|
2001-12-08 04:24:40 +01:00
|
|
|
PostgreSQL documentation
|
1999-07-22 17:09:15 +02:00
|
|
|
-->
|
|
|
|
|
|
|
|
<refentry id="APP-PGDUMP">
|
1999-07-06 19:16:42 +02:00
|
|
|
<refmeta>
|
2002-04-21 21:02:39 +02:00
|
|
|
<refentrytitle>pg_dump</refentrytitle>
|
2000-12-26 00:15:27 +01:00
|
|
|
<manvolnum>1</manvolnum>
|
1999-07-06 19:16:42 +02:00
|
|
|
<refmiscinfo>Application</refmiscinfo>
|
|
|
|
</refmeta>
|
2001-03-06 19:55:57 +01:00
|
|
|
|
1999-07-06 19:16:42 +02:00
|
|
|
<refnamediv>
|
2001-03-06 19:55:57 +01:00
|
|
|
<refname>pg_dump</refname>
|
|
|
|
|
1999-07-06 19:16:42 +02:00
|
|
|
<refpurpose>
|
2006-10-10 01:36:59 +02:00
|
|
|
extract a <productname>PostgreSQL</productname> database into a script file or other archive file
|
1999-07-06 19:16:42 +02:00
|
|
|
</refpurpose>
|
|
|
|
</refnamediv>
|
2001-03-06 19:55:57 +01:00
|
|
|
|
2003-08-31 19:32:24 +02:00
|
|
|
<indexterm zone="app-pgdump">
|
|
|
|
<primary>pg_dump</primary>
|
|
|
|
</indexterm>
|
|
|
|
|
1999-07-06 19:16:42 +02:00
|
|
|
<refsynopsisdiv>
|
2001-03-06 19:55:57 +01:00
|
|
|
<cmdsynopsis>
|
|
|
|
<command>pg_dump</command>
|
2010-02-19 04:50:03 +01:00
|
|
|
<arg rep="repeat"><replaceable>connection-option</replaceable></arg>
|
2003-03-24 15:32:51 +01:00
|
|
|
<arg rep="repeat"><replaceable>option</replaceable></arg>
|
2002-08-10 18:57:32 +02:00
|
|
|
<arg><replaceable>dbname</replaceable></arg>
|
2001-03-06 19:55:57 +01:00
|
|
|
</cmdsynopsis>
|
|
|
|
</refsynopsisdiv>
|
|
|
|
|
|
|
|
|
|
|
|
<refsect1 id="pg-dump-description">
|
|
|
|
<title>
|
|
|
|
Description
|
|
|
|
</title>
|
|
|
|
|
|
|
|
<para>
|
2003-04-17 17:34:37 +02:00
|
|
|
<application>pg_dump</application> is a utility for backing up a
|
|
|
|
<productname>PostgreSQL</productname> database. It makes consistent
|
|
|
|
backups even if the database is being used concurrently.
|
|
|
|
<application>pg_dump</application> does not block other users
|
|
|
|
accessing the database (readers or writers).
|
2002-10-12 01:03:48 +02:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2005-01-04 04:58:16 +01:00
|
|
|
Dumps can be output in script or archive file formats. Script
|
|
|
|
dumps are plain-text files containing the SQL commands required
|
2003-04-17 17:34:37 +02:00
|
|
|
to reconstruct the database to the state it was in at the time it was
|
2005-01-04 04:58:16 +01:00
|
|
|
saved. To restore from such a script, feed it to <xref
|
|
|
|
linkend="app-psql">. Script files
|
2003-04-17 17:34:37 +02:00
|
|
|
can be used to reconstruct the database even on other machines and
|
2010-02-19 04:50:03 +01:00
|
|
|
other architectures; with some modifications, even on other SQL
|
2003-04-17 17:34:37 +02:00
|
|
|
database products.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2005-01-04 04:58:16 +01:00
|
|
|
The alternative archive file formats must be used with
|
|
|
|
<xref linkend="app-pgrestore"> to rebuild the database. They
|
2003-04-17 17:34:37 +02:00
|
|
|
allow <application>pg_restore</application> to be selective about
|
|
|
|
what is restored, or even to reorder the items prior to being
|
2005-06-21 22:45:44 +02:00
|
|
|
restored.
|
|
|
|
The archive file formats are designed to be portable across
|
2001-08-22 22:23:24 +02:00
|
|
|
architectures.
|
2001-03-06 19:55:57 +01:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2001-08-22 22:23:24 +02:00
|
|
|
When used with one of the archive file formats and combined with
|
2003-04-17 17:34:37 +02:00
|
|
|
<application>pg_restore</application>,
|
|
|
|
<application>pg_dump</application> provides a flexible archival and
|
2002-10-12 01:03:48 +02:00
|
|
|
transfer mechanism. <application>pg_dump</application> can be used to
|
2003-04-17 17:34:37 +02:00
|
|
|
backup an entire database, then <application>pg_restore</application>
|
|
|
|
can be used to examine the archive and/or select which parts of the
|
|
|
|
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
|
2011-01-23 22:10:15 +01:00
|
|
|
by default.
|
2001-08-22 22:23:24 +02:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2003-03-24 15:32:51 +01:00
|
|
|
While running <application>pg_dump</application>, one should examine the
|
2001-08-22 22:23:24 +02:00
|
|
|
output for any warnings (printed on standard error), especially in
|
|
|
|
light of the limitations listed below.
|
|
|
|
</para>
|
|
|
|
|
2002-08-27 20:57:26 +02:00
|
|
|
</refsect1>
|
2001-03-06 19:55:57 +01:00
|
|
|
|
2002-08-27 20:57:26 +02:00
|
|
|
<refsect1 id="pg-dump-options">
|
|
|
|
<title>Options</title>
|
2001-03-06 19:55:57 +01:00
|
|
|
|
2002-08-27 20:57:26 +02:00
|
|
|
<para>
|
2005-01-04 04:58:16 +01:00
|
|
|
The following command-line options control the content and
|
|
|
|
format of the output.
|
1999-07-06 19:16:42 +02:00
|
|
|
|
|
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
|
|
|
<term><replaceable class="parameter">dbname</replaceable></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
2005-01-04 04:58:16 +01:00
|
|
|
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.
|
1999-07-06 19:16:42 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2002-03-22 20:20:45 +01:00
|
|
|
<term><option>-a</></term>
|
|
|
|
<term><option>--data-only</></term>
|
1999-07-06 19:16:42 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2005-01-04 04:58:16 +01:00
|
|
|
Dump only the data, not the schema (data definitions).
|
1999-07-06 19:16:42 +02:00
|
|
|
</para>
|
2001-10-24 00:11:22 +02:00
|
|
|
|
|
|
|
<para>
|
2011-12-17 01:09:38 +01:00
|
|
|
This option is equivalent to specifying <option>--section=data</>.
|
2001-10-24 00:11:22 +02:00
|
|
|
</para>
|
1999-07-06 19:16:42 +02:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2006-10-10 01:36:59 +02:00
|
|
|
<varlistentry>
|
|
|
|
<term><option>-b</></term>
|
|
|
|
<term><option>--blobs</></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Include large objects in the dump. This is the default behavior
|
|
|
|
except when <option>--schema</>, <option>--table</>, or
|
|
|
|
<option>--schema-only</> is specified, so the <option>-b</>
|
|
|
|
switch is only useful to add large objects to selective dumps.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2001-03-05 19:42:57 +01:00
|
|
|
<varlistentry>
|
2002-03-22 20:20:45 +01:00
|
|
|
<term><option>-c</option></term>
|
|
|
|
<term><option>--clean</option></term>
|
2001-03-05 19:42:57 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2001-10-24 00:11:22 +02:00
|
|
|
Output commands to clean (drop)
|
2011-05-19 00:14:45 +02:00
|
|
|
database objects prior to outputting the commands for creating them.
|
2011-03-11 13:05:38 +01:00
|
|
|
(Restore might generate some harmless errors.)
|
2001-10-24 00:11:22 +02:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2001-11-28 21:49:10 +01:00
|
|
|
This option is only meaningful for the plain-text format. For
|
Update reference documentation on may/can/might:
Standard English uses "may", "can", and "might" in different ways:
may - permission, "You may borrow my rake."
can - ability, "I can lift that log."
might - possibility, "It might rain today."
Unfortunately, in conversational English, their use is often mixed, as
in, "You may use this variable to do X", when in fact, "can" is a better
choice. Similarly, "It may crash" is better stated, "It might crash".
2007-02-01 00:26:05 +01:00
|
|
|
the archive formats, you can specify the option when you
|
2001-10-24 00:11:22 +02:00
|
|
|
call <command>pg_restore</command>.
|
2001-03-05 19:42:57 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2002-03-22 20:20:45 +01:00
|
|
|
<term><option>-C</></term>
|
|
|
|
<term><option>--create</></term>
|
2001-03-05 19:42:57 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2005-01-04 04:58:16 +01:00
|
|
|
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.)
|
2001-10-24 00:11:22 +02:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2001-11-28 21:49:10 +01:00
|
|
|
This option is only meaningful for the plain-text format. For
|
Update reference documentation on may/can/might:
Standard English uses "may", "can", and "might" in different ways:
may - permission, "You may borrow my rake."
can - ability, "I can lift that log."
might - possibility, "It might rain today."
Unfortunately, in conversational English, their use is often mixed, as
in, "You may use this variable to do X", when in fact, "can" is a better
choice. Similarly, "It may crash" is better stated, "It might crash".
2007-02-01 00:26:05 +01:00
|
|
|
the archive formats, you can specify the option when you
|
2001-10-24 00:11:22 +02:00
|
|
|
call <command>pg_restore</command>.
|
2001-03-05 19:42:57 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2005-11-01 22:09:51 +01:00
|
|
|
<varlistentry>
|
|
|
|
<term><option>-E <replaceable class="parameter">encoding</replaceable></option></term>
|
|
|
|
<term><option>--encoding=<replaceable class="parameter">encoding</replaceable></option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Create the dump in the specified character set encoding. By default,
|
|
|
|
the dump is created in the database encoding. (Another way to get the
|
|
|
|
same result is to set the <envar>PGCLIENTENCODING</envar> environment
|
|
|
|
variable to the desired dump encoding.)
|
|
|
|
</para>
|
|
|
|
</listitem>
|
2005-07-10 17:08:52 +02:00
|
|
|
</varlistentry>
|
|
|
|
|
2001-03-05 19:42:57 +01:00
|
|
|
<varlistentry>
|
2002-03-22 20:20:45 +01:00
|
|
|
<term><option>-f <replaceable class="parameter">file</replaceable></option></term>
|
|
|
|
<term><option>--file=<replaceable class="parameter">file</replaceable></option></term>
|
2001-03-05 19:42:57 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2011-01-23 22:10:15 +01:00
|
|
|
Send output to the specified file. This parameter can be omitted for
|
|
|
|
file based output formats, in which case the standard output is used.
|
|
|
|
It must be given for the directory output format however, where it
|
|
|
|
specifies the target directory instead of a file. In this case the
|
|
|
|
directory is created by <command>pg_dump</command> and must not exist
|
|
|
|
before.
|
2001-03-05 19:42:57 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2002-03-22 20:20:45 +01:00
|
|
|
<term><option>-F <replaceable class="parameter">format</replaceable></option></term>
|
|
|
|
<term><option>--format=<replaceable class="parameter">format</replaceable></option></term>
|
2001-03-05 19:42:57 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2001-08-22 22:23:24 +02:00
|
|
|
Selects the format of the output.
|
2005-01-04 04:58:16 +01:00
|
|
|
<replaceable>format</replaceable> can be one of the following:
|
2001-03-05 19:42:57 +01:00
|
|
|
|
|
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
2003-03-24 15:32:51 +01:00
|
|
|
<term><literal>p</></term>
|
2006-03-17 17:02:47 +01:00
|
|
|
<term><literal>plain</></term>
|
2001-03-05 19:42:57 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2006-10-10 01:36:59 +02:00
|
|
|
Output a plain-text <acronym>SQL</acronym> script file (the default).
|
2001-03-05 19:42:57 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2006-05-07 01:25:37 +02:00
|
|
|
<term><literal>c</></term>
|
|
|
|
<term><literal>custom</></term>
|
2001-03-05 19:42:57 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2010-02-23 18:28:09 +01:00
|
|
|
Output a custom-format archive suitable for input into
|
|
|
|
<application>pg_restore</application>.
|
2011-01-23 22:10:15 +01:00
|
|
|
Together with the directory output format, this is the most flexible
|
|
|
|
output format in that it allows manual selection and reordering of
|
|
|
|
archived items during restore. This format is also compressed by
|
|
|
|
default.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term><literal>d</></term>
|
|
|
|
<term><literal>directory</></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Output a directory-format archive suitable for input into
|
|
|
|
<application>pg_restore</application>. This will create a directory
|
|
|
|
with one file for each table and blob being dumped, plus a
|
|
|
|
so-called Table of Contents file describing the dumped objects in a
|
|
|
|
machine-readable format that <application>pg_restore</application>
|
|
|
|
can read. A directory format archive can be manipulated with
|
|
|
|
standard Unix tools; for example, files in an uncompressed archive
|
|
|
|
can be compressed with the <application>gzip</application> tool.
|
|
|
|
This format is compressed by default.
|
2001-03-05 19:42:57 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2006-05-07 01:25:37 +02:00
|
|
|
<term><literal>t</></term>
|
|
|
|
<term><literal>tar</></term>
|
2001-03-05 19:42:57 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2010-02-23 18:28:09 +01:00
|
|
|
Output a <command>tar</command>-format archive suitable for input
|
2011-01-23 22:10:15 +01:00
|
|
|
into <application>pg_restore</application>. The tar-format is
|
|
|
|
compatible with the directory-format; extracting a tar-format
|
|
|
|
archive produces a valid directory-format archive.
|
|
|
|
However, the tar-format does not support compression and has a
|
|
|
|
limit of 8 GB on the size of individual tables. Also, the relative
|
|
|
|
order of table data items cannot be changed during restore.
|
2001-03-05 19:42:57 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2011-08-07 09:49:45 +02:00
|
|
|
</variablelist></para>
|
2001-03-05 19:42:57 +01:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
1999-07-06 19:16:42 +02:00
|
|
|
|
2000-04-04 07:22:46 +02:00
|
|
|
<varlistentry>
|
2002-03-22 20:20:45 +01:00
|
|
|
<term><option>-i</></term>
|
|
|
|
<term><option>--ignore-version</></term>
|
2000-04-04 07:22:46 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2008-04-13 05:49:22 +02:00
|
|
|
A deprecated option that is now ignored.
|
2000-04-04 07:22:46 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2003-02-13 05:54:16 +01:00
|
|
|
<varlistentry>
|
2005-01-17 05:30:37 +01:00
|
|
|
<term><option>-n <replaceable class="parameter">schema</replaceable></option></term>
|
2003-02-13 05:54:16 +01:00
|
|
|
<term><option>--schema=<replaceable class="parameter">schema</replaceable></option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
2006-10-10 01:36:59 +02:00
|
|
|
Dump only schemas matching <replaceable
|
|
|
|
class="parameter">schema</replaceable>; this selects both the
|
|
|
|
schema itself, and all its contained objects. When this option is
|
|
|
|
not specified, all non-system schemas in the target database will be
|
|
|
|
dumped. Multiple schemas can be
|
|
|
|
selected by writing multiple <option>-n</> switches. Also, the
|
|
|
|
<replaceable class="parameter">schema</replaceable> parameter is
|
|
|
|
interpreted as a pattern according to the same rules used by
|
|
|
|
<application>psql</>'s <literal>\d</> commands (see <xref
|
|
|
|
linkend="APP-PSQL-patterns" endterm="APP-PSQL-patterns-title">),
|
|
|
|
so multiple schemas can also be selected by writing wildcard characters
|
|
|
|
in the pattern. When using wildcards, be careful to quote the pattern
|
2011-03-11 01:40:23 +01:00
|
|
|
if needed to prevent the shell from expanding the wildcards; see
|
|
|
|
<xref linkend="pg-dump-examples" endterm="pg-dump-examples-title">.
|
2003-02-13 05:54:16 +01:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<note>
|
|
|
|
<para>
|
2006-10-10 01:36:59 +02:00
|
|
|
When <option>-n</> is specified, <application>pg_dump</application>
|
|
|
|
makes no attempt to dump any other database objects that the selected
|
Update reference documentation on may/can/might:
Standard English uses "may", "can", and "might" in different ways:
may - permission, "You may borrow my rake."
can - ability, "I can lift that log."
might - possibility, "It might rain today."
Unfortunately, in conversational English, their use is often mixed, as
in, "You may use this variable to do X", when in fact, "can" is a better
choice. Similarly, "It may crash" is better stated, "It might crash".
2007-02-01 00:26:05 +01:00
|
|
|
schema(s) might depend upon. Therefore, there is no guarantee
|
2006-10-10 01:36:59 +02:00
|
|
|
that the results of a specific-schema dump can be successfully
|
|
|
|
restored by themselves into a clean database.
|
|
|
|
</para>
|
|
|
|
</note>
|
|
|
|
|
|
|
|
<note>
|
|
|
|
<para>
|
|
|
|
Non-schema objects such as blobs are not dumped when <option>-n</> is
|
|
|
|
specified. You can add blobs back to the dump with the
|
|
|
|
<option>--blobs</> switch.
|
2003-02-13 05:54:16 +01:00
|
|
|
</para>
|
|
|
|
</note>
|
2006-10-10 01:36:59 +02:00
|
|
|
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term><option>-N <replaceable class="parameter">schema</replaceable></option></term>
|
|
|
|
<term><option>--exclude-schema=<replaceable class="parameter">schema</replaceable></option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Do not dump any schemas matching the <replaceable
|
|
|
|
class="parameter">schema</replaceable> pattern. The pattern is
|
|
|
|
interpreted according to the same rules as for <option>-n</>.
|
|
|
|
<option>-N</> can be given more than once to exclude schemas
|
|
|
|
matching any of several patterns.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
When both <option>-n</> and <option>-N</> are given, the behavior
|
|
|
|
is to dump just the schemas that match at least one <option>-n</>
|
|
|
|
switch but no <option>-N</> switches. If <option>-N</> appears
|
|
|
|
without <option>-n</>, then schemas matching <option>-N</> are
|
|
|
|
excluded from what is otherwise a normal dump.
|
|
|
|
</para>
|
2003-02-13 05:54:16 +01:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2001-03-05 19:42:57 +01:00
|
|
|
<varlistentry>
|
2002-03-22 20:20:45 +01:00
|
|
|
<term><option>-o</></term>
|
|
|
|
<term><option>--oids</></term>
|
2001-03-05 19:42:57 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2005-01-04 04:58:16 +01:00
|
|
|
Dump object identifiers (<acronym>OID</acronym>s) as part of the
|
|
|
|
data for every table. Use this option if your application references
|
|
|
|
the <acronym>OID</>
|
|
|
|
columns in some way (e.g., in a foreign key constraint).
|
|
|
|
Otherwise, this option should not be used.
|
2001-03-05 19:42:57 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2002-03-22 20:20:45 +01:00
|
|
|
<term><option>-O</></term>
|
|
|
|
<term><option>--no-owner</option></term>
|
2001-03-05 19:42:57 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2003-09-24 00:48:53 +02:00
|
|
|
Do not output commands to set
|
2005-01-04 04:58:16 +01:00
|
|
|
ownership of objects to match the original database.
|
|
|
|
By default, <application>pg_dump</application> issues
|
2006-10-10 01:36:59 +02:00
|
|
|
<command>ALTER OWNER</> or
|
2005-01-04 04:58:16 +01:00
|
|
|
<command>SET SESSION AUTHORIZATION</command>
|
|
|
|
statements to set ownership of created database 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).
|
|
|
|
To make a script that can be restored by any user, but will give
|
|
|
|
that user ownership of all the objects, specify <option>-O</>.
|
2001-08-22 22:23:24 +02:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2001-11-28 21:49:10 +01:00
|
|
|
This option is only meaningful for the plain-text format. For
|
Update reference documentation on may/can/might:
Standard English uses "may", "can", and "might" in different ways:
may - permission, "You may borrow my rake."
can - ability, "I can lift that log."
might - possibility, "It might rain today."
Unfortunately, in conversational English, their use is often mixed, as
in, "You may use this variable to do X", when in fact, "can" is a better
choice. Similarly, "It may crash" is better stated, "It might crash".
2007-02-01 00:26:05 +01:00
|
|
|
the archive formats, you can specify the option when you
|
2001-08-22 22:23:24 +02:00
|
|
|
call <command>pg_restore</command>.
|
2001-03-05 19:42:57 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2002-03-22 20:20:45 +01:00
|
|
|
<term><option>-R</option></term>
|
|
|
|
<term><option>--no-reconnect</option></term>
|
2001-03-05 19:42:57 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2003-09-24 00:48:53 +02:00
|
|
|
This option is obsolete but still accepted for backwards
|
2005-01-04 04:58:16 +01:00
|
|
|
compatibility.
|
2001-03-05 19:42:57 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
1999-07-06 19:16:42 +02:00
|
|
|
<varlistentry>
|
2002-03-22 20:20:45 +01:00
|
|
|
<term><option>-s</option></term>
|
|
|
|
<term><option>--schema-only</option></term>
|
1999-07-06 19:16:42 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2005-01-04 04:58:16 +01:00
|
|
|
Dump only the object definitions (schema), not data.
|
1999-07-06 19:16:42 +02:00
|
|
|
</para>
|
2011-12-14 15:23:17 +01:00
|
|
|
<para>
|
|
|
|
To exclude table data for only a subset of tables in the database,
|
|
|
|
see <option>--exclude-table-data</>.
|
|
|
|
</para>
|
2011-12-17 01:09:38 +01:00
|
|
|
<para>
|
|
|
|
This option is equivalent to specifying
|
|
|
|
<option>--section=pre-data --section=post-data</>.
|
|
|
|
</para>
|
1999-07-06 19:16:42 +02:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2011-12-17 01:09:38 +01:00
|
|
|
<varlistentry>
|
|
|
|
<term><option>--section=<replaceable class="parameter">sectionname</replaceable></option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Only dump the named section. The name can be one of <option>pre-data</>, <option>data</>
|
|
|
|
and <option>post-data</>.
|
|
|
|
This option can be specified more than once. The default is to dump all sections.
|
|
|
|
</para>
|
|
|
|
<para>
|
|
|
|
Post-data items consist of definitions of indexes, triggers, rules
|
|
|
|
and constraints other than check constraints.
|
|
|
|
Pre-data items consist of all other data definition items.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2001-03-05 19:42:57 +01:00
|
|
|
<varlistentry>
|
2002-03-22 20:20:45 +01:00
|
|
|
<term><option>-S <replaceable class="parameter">username</replaceable></option></term>
|
|
|
|
<term><option>--superuser=<replaceable class="parameter">username</replaceable></option></term>
|
2001-03-05 19:42:57 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2002-05-11 00:36:27 +02:00
|
|
|
Specify the superuser user name to use when disabling triggers.
|
2005-01-04 04:58:16 +01:00
|
|
|
This is only relevant if <option>--disable-triggers</> is used.
|
|
|
|
(Usually, it's better to leave this out, and instead start the
|
|
|
|
resulting script as superuser.)
|
2001-03-05 19:42:57 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2002-03-22 20:20:45 +01:00
|
|
|
<term><option>-t <replaceable class="parameter">table</replaceable></option></term>
|
|
|
|
<term><option>--table=<replaceable class="parameter">table</replaceable></option></term>
|
2001-03-05 19:42:57 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2011-01-02 05:48:11 +01:00
|
|
|
Dump only tables (or views or sequences or foreign tables) matching
|
|
|
|
<replaceable class="parameter">table</replaceable>. Multiple tables
|
|
|
|
can be selected by writing multiple <option>-t</> switches. Also, the
|
2006-10-10 01:36:59 +02:00
|
|
|
<replaceable class="parameter">table</replaceable> parameter is
|
|
|
|
interpreted as a pattern according to the same rules used by
|
|
|
|
<application>psql</>'s <literal>\d</> commands (see <xref
|
|
|
|
linkend="APP-PSQL-patterns" endterm="APP-PSQL-patterns-title">),
|
|
|
|
so multiple tables can also be selected by writing wildcard characters
|
|
|
|
in the pattern. When using wildcards, be careful to quote the pattern
|
2011-03-11 01:40:23 +01:00
|
|
|
if needed to prevent the shell from expanding the wildcards; see
|
|
|
|
<xref linkend="pg-dump-examples" endterm="pg-dump-examples-title">.
|
2003-02-13 05:54:16 +01:00
|
|
|
</para>
|
|
|
|
|
2006-08-01 20:05:04 +02:00
|
|
|
<para>
|
2006-10-10 01:36:59 +02:00
|
|
|
The <option>-n</> and <option>-N</> switches have no effect when
|
|
|
|
<option>-t</> is used, because tables selected by <option>-t</> will
|
|
|
|
be dumped regardless of those switches, and non-table objects will not
|
|
|
|
be dumped.
|
2006-08-01 20:05:04 +02:00
|
|
|
</para>
|
|
|
|
|
2003-02-13 05:54:16 +01:00
|
|
|
<note>
|
|
|
|
<para>
|
2006-10-10 01:36:59 +02:00
|
|
|
When <option>-t</> is specified, <application>pg_dump</application>
|
|
|
|
makes no attempt to dump any other database objects that the selected
|
Update reference documentation on may/can/might:
Standard English uses "may", "can", and "might" in different ways:
may - permission, "You may borrow my rake."
can - ability, "I can lift that log."
might - possibility, "It might rain today."
Unfortunately, in conversational English, their use is often mixed, as
in, "You may use this variable to do X", when in fact, "can" is a better
choice. Similarly, "It may crash" is better stated, "It might crash".
2007-02-01 00:26:05 +01:00
|
|
|
table(s) might depend upon. Therefore, there is no guarantee
|
2006-08-01 20:05:04 +02:00
|
|
|
that the results of a specific-table dump can be successfully
|
2003-02-13 05:54:16 +01:00
|
|
|
restored by themselves into a clean database.
|
|
|
|
</para>
|
|
|
|
</note>
|
2006-10-10 01:36:59 +02:00
|
|
|
|
|
|
|
<note>
|
|
|
|
<para>
|
|
|
|
The behavior of the <option>-t</> switch is not entirely upward
|
|
|
|
compatible with pre-8.2 <productname>PostgreSQL</productname>
|
|
|
|
versions. Formerly, writing <literal>-t tab</> would dump all
|
|
|
|
tables named <literal>tab</>, but now it just dumps whichever one
|
|
|
|
is visible in your default search path. To get the old behavior
|
|
|
|
you can write <literal>-t '*.tab'</>. Also, you must write something
|
|
|
|
like <literal>-t sch.tab</> to select a table in a particular schema,
|
|
|
|
rather than the old locution of <literal>-n sch -t tab</>.
|
|
|
|
</para>
|
|
|
|
</note>
|
2001-03-05 19:42:57 +01:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2006-08-01 20:05:04 +02:00
|
|
|
<varlistentry>
|
|
|
|
<term><option>-T <replaceable class="parameter">table</replaceable></option></term>
|
|
|
|
<term><option>--exclude-table=<replaceable class="parameter">table</replaceable></option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
2006-10-10 01:36:59 +02:00
|
|
|
Do not dump any tables matching the <replaceable
|
|
|
|
class="parameter">table</replaceable> pattern. The pattern is
|
|
|
|
interpreted according to the same rules as for <option>-t</>.
|
|
|
|
<option>-T</> can be given more than once to exclude tables
|
|
|
|
matching any of several patterns.
|
2006-08-01 20:05:04 +02:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2006-10-10 01:36:59 +02:00
|
|
|
When both <option>-t</> and <option>-T</> are given, the behavior
|
|
|
|
is to dump just the tables that match at least one <option>-t</>
|
|
|
|
switch but no <option>-T</> switches. If <option>-T</> appears
|
|
|
|
without <option>-t</>, then tables matching <option>-T</> are
|
|
|
|
excluded from what is otherwise a normal dump.
|
2006-08-01 20:05:04 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
1999-07-06 19:16:42 +02:00
|
|
|
<varlistentry>
|
2002-03-22 20:20:45 +01:00
|
|
|
<term><option>-v</></term>
|
|
|
|
<term><option>--verbose</></term>
|
1999-07-06 19:16:42 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2005-01-04 04:58:16 +01:00
|
|
|
Specifies verbose mode. This will cause
|
|
|
|
<application>pg_dump</application> to output detailed object
|
2006-10-10 01:36:59 +02:00
|
|
|
comments and start/stop times to the dump file, and progress
|
2004-06-07 22:35:57 +02:00
|
|
|
messages to standard error.
|
1999-07-06 19:16:42 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2010-02-19 15:36:45 +01:00
|
|
|
<varlistentry>
|
|
|
|
<term><option>-V</></term>
|
|
|
|
<term><option>--version</></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Print the <application>pg_dump</application> version and exit.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
1999-07-06 19:16:42 +02:00
|
|
|
<varlistentry>
|
2002-03-22 20:20:45 +01:00
|
|
|
<term><option>-x</></term>
|
|
|
|
<term><option>--no-privileges</></term>
|
|
|
|
<term><option>--no-acl</></term>
|
1999-07-06 19:16:42 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2005-01-04 04:58:16 +01:00
|
|
|
Prevent dumping of access privileges (grant/revoke commands).
|
2001-08-22 22:23:24 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2008-07-20 20:43:30 +02:00
|
|
|
<varlistentry>
|
|
|
|
<term><option>-Z <replaceable class="parameter">0..9</replaceable></option></term>
|
|
|
|
<term><option>--compress=<replaceable class="parameter">0..9</replaceable></option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
2008-08-26 02:03:15 +02:00
|
|
|
Specify the compression level to use. Zero means no compression.
|
|
|
|
For the custom archive format, this specifies compression of
|
|
|
|
individual table-data segments, and the default is to compress
|
|
|
|
at a moderate level.
|
|
|
|
For plain text output, setting a nonzero compression level causes
|
|
|
|
the entire output file to be compressed, as though it had been
|
|
|
|
fed through <application>gzip</>; but the default is not to compress.
|
|
|
|
The tar archive format currently does not support compression at all.
|
2008-07-20 20:43:30 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2009-03-04 12:57:00 +01:00
|
|
|
<varlistentry>
|
|
|
|
<term><option>--binary-upgrade</option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
This option is for use by in-place upgrade utilities. Its use
|
|
|
|
for other purposes is not recommended or supported. The
|
|
|
|
behavior of the option may change in future releases without
|
|
|
|
notice.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2009-03-22 17:44:26 +01:00
|
|
|
<varlistentry>
|
|
|
|
<term><option>--column-inserts</option></term>
|
|
|
|
<term><option>--attribute-inserts</option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Dump data as <command>INSERT</command> commands with explicit
|
|
|
|
column names (<literal>INSERT INTO
|
|
|
|
<replaceable>table</replaceable>
|
|
|
|
(<replaceable>column</replaceable>, ...) VALUES
|
|
|
|
...</literal>). This will make restoration very slow; it is mainly
|
|
|
|
useful for making dumps that can be loaded into
|
|
|
|
non-<productname>PostgreSQL</productname> databases.
|
2010-02-19 04:50:03 +01:00
|
|
|
However, since this option generates a separate command for each row,
|
2009-03-22 17:44:26 +01:00
|
|
|
an error in reloading a row causes only that row to be lost rather
|
|
|
|
than the entire table contents.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2001-08-22 22:23:24 +02:00
|
|
|
<varlistentry>
|
2004-03-23 23:06:08 +01:00
|
|
|
<term><option>--disable-dollar-quoting</></term>
|
2001-08-22 22:23:24 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2004-03-23 23:06:08 +01:00
|
|
|
This option disables the use of dollar quoting for function bodies,
|
|
|
|
and forces them to be quoted using SQL standard string syntax.
|
1999-07-06 19:16:42 +02:00
|
|
|
</para>
|
2008-07-20 20:43:30 +02:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2001-03-05 19:42:57 +01:00
|
|
|
|
2002-05-11 00:36:27 +02:00
|
|
|
<varlistentry>
|
|
|
|
<term><option>--disable-triggers</></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
This option is only relevant when creating a data-only dump.
|
2004-03-23 23:06:08 +01:00
|
|
|
It instructs <application>pg_dump</application> 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.
|
2002-05-11 00:36:27 +02:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
Presently, the commands emitted for <option>--disable-triggers</>
|
2004-03-23 23:06:08 +01:00
|
|
|
must be done as superuser. So, you should also specify
|
|
|
|
a superuser name with <option>-S</>, or preferably be careful to
|
|
|
|
start the resulting script as a superuser.
|
2002-05-11 00:36:27 +02:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
This option is only meaningful for the plain-text format. For
|
Update reference documentation on may/can/might:
Standard English uses "may", "can", and "might" in different ways:
may - permission, "You may borrow my rake."
can - ability, "I can lift that log."
might - possibility, "It might rain today."
Unfortunately, in conversational English, their use is often mixed, as
in, "You may use this variable to do X", when in fact, "can" is a better
choice. Similarly, "It may crash" is better stated, "It might crash".
2007-02-01 00:26:05 +01:00
|
|
|
the archive formats, you can specify the option when you
|
2002-05-11 00:36:27 +02:00
|
|
|
call <command>pg_restore</command>.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2011-12-14 15:23:17 +01:00
|
|
|
<varlistentry>
|
|
|
|
<term><option>--exclude-table-data=<replaceable class="parameter">table</replaceable></option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Do not dump data for any tables matching the <replaceable
|
|
|
|
class="parameter">table</replaceable> pattern. The pattern is
|
|
|
|
interpreted according to the same rules as for <option>-t</>.
|
|
|
|
<option>--exclude-table-data</> can be given more than once to
|
|
|
|
exclude tables matching any of several patterns. This option is
|
|
|
|
useful when you need the definition of a particular table even
|
|
|
|
though you do not need the data in it.
|
|
|
|
</para>
|
|
|
|
<para>
|
|
|
|
To exclude data for all tables in the database, see <option>--schema-only</>.
|
2011-12-14 22:49:20 +01:00
|
|
|
</para>
|
2011-12-14 15:23:17 +01:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2011-05-25 20:53:26 +02:00
|
|
|
<varlistentry>
|
|
|
|
<term><option>--inserts</option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Dump data as <command>INSERT</command> commands (rather
|
|
|
|
than <command>COPY</command>). This will make restoration very slow;
|
|
|
|
it is mainly useful for making dumps that can be loaded into
|
|
|
|
non-<productname>PostgreSQL</productname> databases.
|
|
|
|
However, since this option generates a separate command for each row,
|
|
|
|
an error in reloading a row causes only that row to be lost rather
|
|
|
|
than the entire table contents.
|
|
|
|
Note that
|
|
|
|
the restore might fail altogether if you have rearranged column order.
|
|
|
|
The <option>--column-inserts</option> option is safe against column
|
|
|
|
order changes, though even slower.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2008-07-20 20:43:30 +02:00
|
|
|
<varlistentry>
|
|
|
|
<term><option>--lock-wait-timeout=<replaceable class="parameter">timeout</replaceable></option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Do not wait forever to acquire shared table locks at the beginning of
|
|
|
|
the dump. Instead fail if unable to lock a table within the specified
|
|
|
|
<replaceable class="parameter">timeout</>. The timeout may be
|
|
|
|
specified in any of the formats accepted by <command>SET
|
|
|
|
statement_timeout</>. (Allowed values vary depending on the server
|
|
|
|
version you are dumping from, but an integer number of milliseconds
|
|
|
|
is accepted by all versions since 7.3. This option is ignored when
|
|
|
|
dumping from a pre-7.3 server.)
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
Implement genuine serializable isolation level.
Until now, our Serializable mode has in fact been what's called Snapshot
Isolation, which allows some anomalies that could not occur in any
serialized ordering of the transactions. This patch fixes that using a
method called Serializable Snapshot Isolation, based on research papers by
Michael J. Cahill (see README-SSI for full references). In Serializable
Snapshot Isolation, transactions run like they do in Snapshot Isolation,
but a predicate lock manager observes the reads and writes performed and
aborts transactions if it detects that an anomaly might occur. This method
produces some false positives, ie. it sometimes aborts transactions even
though there is no anomaly.
To track reads we implement predicate locking, see storage/lmgr/predicate.c.
Whenever a tuple is read, a predicate lock is acquired on the tuple. Shared
memory is finite, so when a transaction takes many tuple-level locks on a
page, the locks are promoted to a single page-level lock, and further to a
single relation level lock if necessary. To lock key values with no matching
tuple, a sequential scan always takes a relation-level lock, and an index
scan acquires a page-level lock that covers the search key, whether or not
there are any matching keys at the moment.
A predicate lock doesn't conflict with any regular locks or with another
predicate locks in the normal sense. They're only used by the predicate lock
manager to detect the danger of anomalies. Only serializable transactions
participate in predicate locking, so there should be no extra overhead for
for other transactions.
Predicate locks can't be released at commit, but must be remembered until
all the transactions that overlapped with it have completed. That means that
we need to remember an unbounded amount of predicate locks, so we apply a
lossy but conservative method of tracking locks for committed transactions.
If we run short of shared memory, we overflow to a new "pg_serial" SLRU
pool.
We don't currently allow Serializable transactions in Hot Standby mode.
That would be hard, because even read-only transactions can cause anomalies
that wouldn't otherwise occur.
Serializable isolation mode now means the new fully serializable level.
Repeatable Read gives you the old Snapshot Isolation level that we have
always had.
Kevin Grittner and Dan Ports, reviewed by Jeff Davis, Heikki Linnakangas and
Anssi Kääriäinen
2011-02-07 22:46:51 +01:00
|
|
|
<varlistentry>
|
2011-05-25 20:53:26 +02:00
|
|
|
<term><option>--no-security-labels</option></term>
|
Implement genuine serializable isolation level.
Until now, our Serializable mode has in fact been what's called Snapshot
Isolation, which allows some anomalies that could not occur in any
serialized ordering of the transactions. This patch fixes that using a
method called Serializable Snapshot Isolation, based on research papers by
Michael J. Cahill (see README-SSI for full references). In Serializable
Snapshot Isolation, transactions run like they do in Snapshot Isolation,
but a predicate lock manager observes the reads and writes performed and
aborts transactions if it detects that an anomaly might occur. This method
produces some false positives, ie. it sometimes aborts transactions even
though there is no anomaly.
To track reads we implement predicate locking, see storage/lmgr/predicate.c.
Whenever a tuple is read, a predicate lock is acquired on the tuple. Shared
memory is finite, so when a transaction takes many tuple-level locks on a
page, the locks are promoted to a single page-level lock, and further to a
single relation level lock if necessary. To lock key values with no matching
tuple, a sequential scan always takes a relation-level lock, and an index
scan acquires a page-level lock that covers the search key, whether or not
there are any matching keys at the moment.
A predicate lock doesn't conflict with any regular locks or with another
predicate locks in the normal sense. They're only used by the predicate lock
manager to detect the danger of anomalies. Only serializable transactions
participate in predicate locking, so there should be no extra overhead for
for other transactions.
Predicate locks can't be released at commit, but must be remembered until
all the transactions that overlapped with it have completed. That means that
we need to remember an unbounded amount of predicate locks, so we apply a
lossy but conservative method of tracking locks for committed transactions.
If we run short of shared memory, we overflow to a new "pg_serial" SLRU
pool.
We don't currently allow Serializable transactions in Hot Standby mode.
That would be hard, because even read-only transactions can cause anomalies
that wouldn't otherwise occur.
Serializable isolation mode now means the new fully serializable level.
Repeatable Read gives you the old Snapshot Isolation level that we have
always had.
Kevin Grittner and Dan Ports, reviewed by Jeff Davis, Heikki Linnakangas and
Anssi Kääriäinen
2011-02-07 22:46:51 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2011-05-25 20:53:26 +02:00
|
|
|
Do not dump security labels.
|
Implement genuine serializable isolation level.
Until now, our Serializable mode has in fact been what's called Snapshot
Isolation, which allows some anomalies that could not occur in any
serialized ordering of the transactions. This patch fixes that using a
method called Serializable Snapshot Isolation, based on research papers by
Michael J. Cahill (see README-SSI for full references). In Serializable
Snapshot Isolation, transactions run like they do in Snapshot Isolation,
but a predicate lock manager observes the reads and writes performed and
aborts transactions if it detects that an anomaly might occur. This method
produces some false positives, ie. it sometimes aborts transactions even
though there is no anomaly.
To track reads we implement predicate locking, see storage/lmgr/predicate.c.
Whenever a tuple is read, a predicate lock is acquired on the tuple. Shared
memory is finite, so when a transaction takes many tuple-level locks on a
page, the locks are promoted to a single page-level lock, and further to a
single relation level lock if necessary. To lock key values with no matching
tuple, a sequential scan always takes a relation-level lock, and an index
scan acquires a page-level lock that covers the search key, whether or not
there are any matching keys at the moment.
A predicate lock doesn't conflict with any regular locks or with another
predicate locks in the normal sense. They're only used by the predicate lock
manager to detect the danger of anomalies. Only serializable transactions
participate in predicate locking, so there should be no extra overhead for
for other transactions.
Predicate locks can't be released at commit, but must be remembered until
all the transactions that overlapped with it have completed. That means that
we need to remember an unbounded amount of predicate locks, so we apply a
lossy but conservative method of tracking locks for committed transactions.
If we run short of shared memory, we overflow to a new "pg_serial" SLRU
pool.
We don't currently allow Serializable transactions in Hot Standby mode.
That would be hard, because even read-only transactions can cause anomalies
that wouldn't otherwise occur.
Serializable isolation mode now means the new fully serializable level.
Repeatable Read gives you the old Snapshot Isolation level that we have
always had.
Kevin Grittner and Dan Ports, reviewed by Jeff Davis, Heikki Linnakangas and
Anssi Kääriäinen
2011-02-07 22:46:51 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2008-07-20 20:43:30 +02:00
|
|
|
<varlistentry>
|
|
|
|
<term><option>--no-tablespaces</option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Do not output commands to select tablespaces.
|
|
|
|
With this option, all objects will be created in whichever
|
|
|
|
tablespace is the default during restore.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
This option is only meaningful for the plain-text format. For
|
|
|
|
the archive formats, you can specify the option when you
|
|
|
|
call <command>pg_restore</command>.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2010-12-24 13:11:11 +01:00
|
|
|
<varlistentry>
|
2011-05-25 20:53:26 +02:00
|
|
|
<term><option>--no-unlogged-table-data</option></term>
|
2010-12-24 13:11:11 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2011-05-25 20:53:26 +02:00
|
|
|
Do not dump the contents of unlogged tables. This option has no
|
|
|
|
effect on whether or not the table definitions (schema) are dumped;
|
|
|
|
it only suppresses dumping the table data.
|
2010-12-24 13:11:11 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2004-03-23 23:06:08 +01:00
|
|
|
<varlistentry>
|
2011-05-25 20:53:26 +02:00
|
|
|
<term><option>--quote-all-identifiers</></term>
|
2004-03-23 23:06:08 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2011-05-25 20:53:26 +02:00
|
|
|
Force quoting of all identifiers. This may be useful when dumping a
|
|
|
|
database for migration to a future version that may have introduced
|
|
|
|
additional keywords.
|
2004-03-23 23:06:08 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2010-02-19 15:36:45 +01:00
|
|
|
|
2010-12-29 12:48:53 +01:00
|
|
|
<varlistentry>
|
2011-05-25 20:53:26 +02:00
|
|
|
<term><option>--serializable-deferrable</option></term>
|
2010-12-29 12:48:53 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2011-05-25 20:53:26 +02:00
|
|
|
Use a <literal>serializable</literal> transaction for the dump, to
|
|
|
|
ensure that the snapshot used is consistent with later database
|
|
|
|
states; but do this by waiting for a point in the transaction stream
|
|
|
|
at which no anomalies can be present, so that there isn't a risk of
|
|
|
|
the dump failing or causing other transactions to roll back with a
|
|
|
|
<literal>serialization_failure</literal>. See <xref linkend="mvcc">
|
|
|
|
for more information about transaction isolation and concurrency
|
|
|
|
control.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
This option is not beneficial for a dump which is intended only for
|
|
|
|
disaster recovery. It could be useful for a dump used to load a
|
|
|
|
copy of the database for reporting or other read-only load sharing
|
|
|
|
while the original database continues to be updated. Without it the
|
|
|
|
dump may reflect a state which is not consistent with any serial
|
|
|
|
execution of the transactions eventually committed. For example, if
|
|
|
|
batch processing techniques are used, a batch may show as closed in
|
|
|
|
the dump without all of the items which are in the batch appearing.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
This option will make no difference if there are no read-write
|
|
|
|
transactions active when pg_dump is started. If read-write
|
|
|
|
transactions are active, the start of the dump may be delayed for an
|
|
|
|
indeterminate length of time. Once running, performance with or
|
|
|
|
without the switch is the same.
|
2010-12-29 12:48:53 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2010-07-22 03:22:35 +02:00
|
|
|
<varlistentry>
|
2011-05-25 20:53:26 +02:00
|
|
|
<term><option>--use-set-session-authorization</></term>
|
2010-07-22 03:22:35 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2011-05-25 20:53:26 +02:00
|
|
|
Output SQL-standard <command>SET SESSION AUTHORIZATION</> commands
|
|
|
|
instead of <command>ALTER OWNER</> commands to determine object
|
|
|
|
ownership. This makes the dump more standards-compatible, but
|
|
|
|
depending on the history of the objects in the dump, might not restore
|
|
|
|
properly. Also, a dump using <command>SET SESSION AUTHORIZATION</>
|
|
|
|
will certainly require superuser privileges to restore correctly,
|
|
|
|
whereas <command>ALTER OWNER</> requires lesser privileges.
|
2010-07-22 03:22:35 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2010-02-19 15:36:45 +01:00
|
|
|
<varlistentry>
|
|
|
|
<term><option>-?</></term>
|
|
|
|
<term><option>--help</></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Show help about <application>pg_dump</application> command line
|
|
|
|
arguments, and exit.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
1999-07-06 19:16:42 +02:00
|
|
|
</variablelist>
|
|
|
|
</para>
|
2002-08-27 20:57:26 +02:00
|
|
|
|
1999-07-06 19:16:42 +02:00
|
|
|
<para>
|
2002-08-27 20:57:26 +02:00
|
|
|
The following command-line options control the database connection parameters.
|
1999-07-06 19:16:42 +02:00
|
|
|
|
|
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
2002-03-22 20:20:45 +01:00
|
|
|
<term><option>-h <replaceable class="parameter">host</replaceable></option></term>
|
|
|
|
<term><option>--host=<replaceable class="parameter">host</replaceable></option></term>
|
1999-07-06 19:16:42 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2003-03-24 15:32:51 +01:00
|
|
|
Specifies the host name of the machine on which the server is
|
|
|
|
running. If the value begins with a slash, it is used as the
|
|
|
|
directory for the Unix domain socket. The default is taken
|
|
|
|
from the <envar>PGHOST</envar> environment variable, if set,
|
|
|
|
else a Unix domain socket connection is attempted.
|
1999-07-06 19:16:42 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2002-03-22 20:20:45 +01:00
|
|
|
<term><option>-p <replaceable class="parameter">port</replaceable></option></term>
|
|
|
|
<term><option>--port=<replaceable class="parameter">port</replaceable></option></term>
|
1999-07-06 19:16:42 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2005-01-04 04:58:16 +01:00
|
|
|
Specifies the TCP port or local Unix domain socket file
|
|
|
|
extension on which the server is listening for connections.
|
|
|
|
Defaults to the <envar>PGPORT</envar> environment variable, if
|
|
|
|
set, or a compiled-in default.
|
1999-07-06 19:16:42 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2002-03-22 20:20:45 +01:00
|
|
|
<term><option>-U <replaceable>username</replaceable></option></term>
|
2007-02-01 05:39:33 +01:00
|
|
|
<term><option>--username=<replaceable class="parameter">username</replaceable></option></term>
|
1999-07-06 19:16:42 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2007-12-11 20:57:32 +01:00
|
|
|
User name to connect as.
|
2001-05-17 23:12:49 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2009-02-26 17:02:39 +01:00
|
|
|
<varlistentry>
|
|
|
|
<term><option>-w</></term>
|
|
|
|
<term><option>--no-password</></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Never issue a password prompt. If the server requires
|
|
|
|
password authentication and a password is not available by
|
|
|
|
other means such as a <filename>.pgpass</filename> file, the
|
|
|
|
connection attempt will fail. This option can be useful in
|
|
|
|
batch jobs and scripts where no user is present to enter a
|
|
|
|
password.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2001-05-17 23:12:49 +02:00
|
|
|
<varlistentry>
|
2002-03-22 20:20:45 +01:00
|
|
|
<term><option>-W</option></term>
|
2007-02-01 05:39:33 +01:00
|
|
|
<term><option>--password</option></term>
|
2001-05-17 23:12:49 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2007-12-11 20:57:32 +01:00
|
|
|
Force <application>pg_dump</application> to prompt for a
|
2008-07-20 20:43:30 +02:00
|
|
|
password before connecting to a database.
|
2007-12-11 20:57:32 +01:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
This option is never essential, since
|
|
|
|
<application>pg_dump</application> will automatically prompt
|
|
|
|
for a password if the server demands password authentication.
|
|
|
|
However, <application>pg_dump</application> will waste a
|
|
|
|
connection attempt finding out that the server wants a password.
|
|
|
|
In some cases it is worth typing <option>-W</> to avoid the extra
|
|
|
|
connection attempt.
|
1999-07-06 19:16:42 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2009-01-05 17:54:37 +01:00
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term><option>--role=<replaceable class="parameter">rolename</replaceable></option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Specifies a role name to be used to create the dump.
|
|
|
|
This option causes <application>pg_dump</> to issue a
|
|
|
|
<command>SET ROLE</> <replaceable class="parameter">rolename</>
|
|
|
|
command after connecting to the database. It is useful when the
|
|
|
|
authenticated user (specified by <option>-U</>) lacks privileges
|
|
|
|
needed by <application>pg_dump</>, but can switch to a role with
|
|
|
|
the required rights. Some installations have a policy against
|
|
|
|
logging in directly as a superuser, and use of this option allows
|
|
|
|
dumps to be made without violating the policy.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
1999-07-06 19:16:42 +02:00
|
|
|
</variablelist>
|
|
|
|
</para>
|
2001-03-06 19:55:57 +01:00
|
|
|
</refsect1>
|
1999-07-06 19:16:42 +02:00
|
|
|
|
2002-07-28 17:22:21 +02:00
|
|
|
<refsect1>
|
|
|
|
<title>Environment</title>
|
|
|
|
|
|
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
|
|
|
<term><envar>PGDATABASE</envar></term>
|
|
|
|
<term><envar>PGHOST</envar></term>
|
2009-02-07 15:31:30 +01:00
|
|
|
<term><envar>PGOPTIONS</envar></term>
|
2002-07-28 17:22:21 +02:00
|
|
|
<term><envar>PGPORT</envar></term>
|
|
|
|
|
2009-02-07 15:31:30 +01:00
|
|
|
<term><envar>PGUSER</envar></term>
|
2002-07-28 17:22:21 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2003-02-13 05:54:16 +01:00
|
|
|
Default connection parameters.
|
2002-07-28 17:22:21 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
2009-02-07 15:31:30 +01:00
|
|
|
|
2002-07-28 17:22:21 +02:00
|
|
|
</varlistentry>
|
|
|
|
</variablelist>
|
2007-02-20 19:10:59 +01:00
|
|
|
|
|
|
|
<para>
|
|
|
|
This utility, like most other <productname>PostgreSQL</> utilities,
|
2007-03-26 19:23:37 +02:00
|
|
|
also uses the environment variables supported by <application>libpq</>
|
|
|
|
(see <xref linkend="libpq-envars">).
|
2007-02-20 19:10:59 +01:00
|
|
|
</para>
|
|
|
|
|
2002-07-28 17:22:21 +02:00
|
|
|
</refsect1>
|
|
|
|
|
2001-03-06 19:55:57 +01:00
|
|
|
<refsect1 id="app-pgdump-diagnostics">
|
|
|
|
<title>Diagnostics</title>
|
|
|
|
|
2003-03-24 15:32:51 +01:00
|
|
|
<para>
|
|
|
|
<application>pg_dump</application> internally executes
|
|
|
|
<command>SELECT</command> statements. If you have problems running
|
|
|
|
<application>pg_dump</application>, make sure you are able to
|
|
|
|
select information from the database using, for example, <xref
|
2007-02-20 19:10:59 +01:00
|
|
|
linkend="app-psql">. Also, any default connection settings and environment
|
|
|
|
variables used by the <application>libpq</application> front-end
|
|
|
|
library will apply.
|
2003-03-24 15:32:51 +01:00
|
|
|
</para>
|
2009-02-10 01:55:21 +01:00
|
|
|
|
2009-02-07 15:31:30 +01:00
|
|
|
<para>
|
2009-02-07 16:25:51 +01:00
|
|
|
The database activity of <application>pg_dump</application> is
|
|
|
|
normally collected by the statistics collector. If this is
|
2011-02-03 00:06:38 +01:00
|
|
|
undesirable, you can set parameter <varname>track_counts</>
|
2009-02-10 01:55:21 +01:00
|
|
|
to false via <envar>PGOPTIONS</envar> or the <literal>ALTER
|
|
|
|
USER</literal> command.
|
2009-02-07 15:31:30 +01:00
|
|
|
</para>
|
|
|
|
|
1999-07-06 19:16:42 +02:00
|
|
|
</refsect1>
|
|
|
|
|
2001-03-06 19:55:57 +01:00
|
|
|
|
|
|
|
<refsect1 id="pg-dump-notes">
|
|
|
|
<title>Notes</title>
|
2002-02-11 01:14:10 +01:00
|
|
|
|
|
|
|
<para>
|
2003-03-24 15:32:51 +01:00
|
|
|
If your database cluster has any local additions to the <literal>template1</> database,
|
2002-10-12 01:03:48 +02:00
|
|
|
be careful to restore the output of <application>pg_dump</application> into a
|
2002-02-11 01:14:10 +01:00
|
|
|
truly empty database; otherwise you are likely to get errors due to
|
|
|
|
duplicate definitions of the added objects. To make an empty database
|
2003-03-24 15:32:51 +01:00
|
|
|
without any local additions, copy from <literal>template0</> not <literal>template1</>,
|
2002-02-11 01:14:10 +01:00
|
|
|
for example:
|
|
|
|
<programlisting>
|
2002-10-12 01:03:48 +02:00
|
|
|
CREATE DATABASE foo WITH TEMPLATE template0;
|
2002-02-11 01:14:10 +01:00
|
|
|
</programlisting>
|
|
|
|
</para>
|
|
|
|
|
1999-07-06 19:16:42 +02:00
|
|
|
<para>
|
2009-03-22 17:44:26 +01:00
|
|
|
When a data-only dump is chosen and the option <option>--disable-triggers</>
|
2008-08-22 00:25:44 +02:00
|
|
|
is used, <application>pg_dump</application> emits commands
|
2009-03-22 17:44:26 +01:00
|
|
|
to disable triggers on user tables before inserting the data,
|
|
|
|
and then commands to re-enable them after the data has been
|
2008-08-22 00:25:44 +02:00
|
|
|
inserted. If the restore is stopped in the middle, the system
|
|
|
|
catalogs might be left in the wrong state.
|
1999-07-06 19:16:42 +02:00
|
|
|
</para>
|
2002-09-06 23:58:36 +02:00
|
|
|
|
|
|
|
<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
|
2005-01-04 04:58:16 +01:00
|
|
|
this format cannot be used if the textual representation of any one table
|
2002-09-06 23:58:36 +02:00
|
|
|
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>
|
2003-03-18 01:02:11 +01:00
|
|
|
|
|
|
|
<para>
|
2008-08-22 00:25:44 +02:00
|
|
|
The dump file produced by <application>pg_dump</application>
|
|
|
|
does not contain the statistics used by the optimizer to make
|
|
|
|
query planning decisions. Therefore, it is wise to run
|
|
|
|
<command>ANALYZE</command> after restoring from a dump file
|
2010-02-19 04:50:03 +01:00
|
|
|
to ensure optimal performance; see <xref linkend="vacuum-for-statistics">
|
2009-08-07 22:54:31 +02:00
|
|
|
and <xref linkend="autovacuum"> for more information.
|
|
|
|
The dump file also does not
|
2008-08-22 00:25:44 +02:00
|
|
|
contain any <command>ALTER DATABASE ... SET</> commands;
|
|
|
|
these settings are dumped by <xref linkend="app-pg-dumpall">,
|
|
|
|
along with database users and other installation-wide settings.
|
2003-03-18 01:02:11 +01:00
|
|
|
</para>
|
|
|
|
|
2006-05-13 18:19:54 +02:00
|
|
|
<para>
|
2006-10-23 20:10:32 +02:00
|
|
|
Because <application>pg_dump</application> is used to transfer data
|
2006-05-13 18:19:54 +02:00
|
|
|
to newer versions of <productname>PostgreSQL</>, the output of
|
2009-03-22 17:44:26 +01:00
|
|
|
<application>pg_dump</application> can be expected to load into
|
|
|
|
<productname>PostgreSQL</> server versions newer than
|
|
|
|
<application>pg_dump</>'s version. <application>pg_dump</> can also
|
|
|
|
dump from <productname>PostgreSQL</> servers older than its own version.
|
|
|
|
(Currently, servers back to version 7.0 are supported.)
|
|
|
|
However, <application>pg_dump</> cannot dump from
|
|
|
|
<productname>PostgreSQL</> servers newer than its own major version;
|
|
|
|
it will refuse to even try, rather than risk making an invalid dump.
|
|
|
|
Also, it is not guaranteed that <application>pg_dump</>'s output can
|
|
|
|
be loaded into a server of an older major version — not even if the
|
|
|
|
dump was taken from a server of that version. Loading a dump file
|
|
|
|
into an older server may require manual editing of the dump file
|
|
|
|
to remove syntax not understood by the older server.
|
2006-05-13 18:19:54 +02:00
|
|
|
</para>
|
1999-07-06 19:16:42 +02:00
|
|
|
</refsect1>
|
|
|
|
|
2001-03-06 19:55:57 +01:00
|
|
|
<refsect1 id="pg-dump-examples">
|
2011-03-11 01:40:23 +01:00
|
|
|
<title id="pg-dump-examples-title">Examples</title>
|
1999-07-06 19:16:42 +02:00
|
|
|
|
2001-03-06 19:55:57 +01:00
|
|
|
<para>
|
2006-10-10 01:36:59 +02:00
|
|
|
To dump a database called <literal>mydb</> into a SQL-script file:
|
|
|
|
<screen>
|
|
|
|
<prompt>$</prompt> <userinput>pg_dump mydb > db.sql</userinput>
|
|
|
|
</screen>
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
To reload such a script into a (freshly created) database named
|
|
|
|
<literal>newdb</>:
|
|
|
|
|
2001-03-06 19:55:57 +01:00
|
|
|
<screen>
|
2006-10-10 01:36:59 +02:00
|
|
|
<prompt>$</prompt> <userinput>psql -d newdb -f db.sql</userinput>
|
2001-03-06 19:55:57 +01:00
|
|
|
</screen>
|
1999-07-06 19:16:42 +02:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2006-10-10 01:36:59 +02:00
|
|
|
To dump a database into a custom-format archive file:
|
|
|
|
|
|
|
|
<screen>
|
|
|
|
<prompt>$</prompt> <userinput>pg_dump -Fc mydb > db.dump</userinput>
|
|
|
|
</screen>
|
|
|
|
</para>
|
|
|
|
|
2011-01-23 22:10:15 +01:00
|
|
|
<para>
|
|
|
|
To dump a database into a directory-format archive:
|
|
|
|
|
|
|
|
<screen>
|
|
|
|
<prompt>$</prompt> <userinput>pg_dump -Fd mydb -f dumpdir</userinput>
|
|
|
|
</screen>
|
|
|
|
</para>
|
|
|
|
|
2006-10-10 01:36:59 +02:00
|
|
|
<para>
|
|
|
|
To reload an archive file into a (freshly created) database named
|
|
|
|
<literal>newdb</>:
|
|
|
|
|
|
|
|
<screen>
|
|
|
|
<prompt>$</prompt> <userinput>pg_restore -d newdb db.dump</userinput>
|
|
|
|
</screen>
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
To dump a single table named <literal>mytab</>:
|
|
|
|
|
|
|
|
<screen>
|
|
|
|
<prompt>$</prompt> <userinput>pg_dump -t mytab mydb > db.sql</userinput>
|
|
|
|
</screen>
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
To dump all tables whose names start with <literal>emp</> in the
|
|
|
|
<literal>detroit</> schema, except for the table named
|
|
|
|
<literal>employee_log</literal>:
|
|
|
|
|
|
|
|
<screen>
|
|
|
|
<prompt>$</prompt> <userinput>pg_dump -t 'detroit.emp*' -T detroit.employee_log mydb > db.sql</userinput>
|
|
|
|
</screen>
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
To dump all schemas whose names start with <literal>east</> or
|
|
|
|
<literal>west</> and end in <literal>gsm</>, excluding any schemas whose
|
|
|
|
names contain the word <literal>test</>:
|
|
|
|
|
2001-03-06 19:55:57 +01:00
|
|
|
<screen>
|
2006-10-10 01:36:59 +02:00
|
|
|
<prompt>$</prompt> <userinput>pg_dump -n 'east*gsm' -n 'west*gsm' -N '*test*' mydb > db.sql</userinput>
|
2001-03-06 19:55:57 +01:00
|
|
|
</screen>
|
1999-07-06 19:16:42 +02:00
|
|
|
</para>
|
2001-03-05 19:42:57 +01:00
|
|
|
|
|
|
|
<para>
|
2006-10-10 01:36:59 +02:00
|
|
|
The same, using regular expression notation to consolidate the switches:
|
2001-03-05 19:42:57 +01:00
|
|
|
|
2001-03-06 19:55:57 +01:00
|
|
|
<screen>
|
2006-10-10 01:36:59 +02:00
|
|
|
<prompt>$</prompt> <userinput>pg_dump -n '(east|west)*gsm' -N '*test*' mydb > db.sql</userinput>
|
2001-03-06 19:55:57 +01:00
|
|
|
</screen>
|
2001-03-05 19:42:57 +01:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2006-10-10 01:36:59 +02:00
|
|
|
To dump all database objects except for tables whose names begin with
|
|
|
|
<literal>ts_</literal>:
|
2001-03-05 19:42:57 +01:00
|
|
|
|
2001-03-06 19:55:57 +01:00
|
|
|
<screen>
|
2006-10-10 01:36:59 +02:00
|
|
|
<prompt>$</prompt> <userinput>pg_dump -T 'ts_*' mydb > db.sql</userinput>
|
2006-11-28 23:54:18 +01:00
|
|
|
</screen>
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
To specify an upper-case or mixed-case name in <option>-t</> and related
|
|
|
|
switches, you need to double-quote the name; else it will be folded to
|
|
|
|
lower case (see <xref
|
|
|
|
linkend="APP-PSQL-patterns" endterm="APP-PSQL-patterns-title">). But
|
|
|
|
double quotes are special to the shell, so in turn they must be quoted.
|
|
|
|
Thus, to dump a single table with a mixed-case name, you need something
|
|
|
|
like
|
|
|
|
|
|
|
|
<screen>
|
|
|
|
<prompt>$</prompt> <userinput>pg_dump -t '"MixedCaseName"' mydb > mytab.sql</userinput>
|
2011-08-07 09:49:45 +02:00
|
|
|
</screen></para>
|
2001-03-05 19:42:57 +01:00
|
|
|
|
1999-07-06 19:16:42 +02:00
|
|
|
</refsect1>
|
2001-03-06 19:55:57 +01:00
|
|
|
|
|
|
|
<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>
|
|
|
|
</simplelist>
|
|
|
|
</refsect1>
|
|
|
|
|
1999-07-06 19:16:42 +02:00
|
|
|
</refentry>
|