2010-09-20 22:08:53 +02:00
|
|
|
<!-- doc/src/sgml/ref/pg_restore.sgml -->
|
2001-03-06 19:55:57 +01:00
|
|
|
|
2000-10-12 16:09:37 +02:00
|
|
|
<refentry id="APP-PGRESTORE">
|
2014-02-24 03:25:35 +01:00
|
|
|
<indexterm zone="app-pgrestore">
|
|
|
|
<primary>pg_restore</primary>
|
|
|
|
</indexterm>
|
|
|
|
|
2000-10-12 16:09:37 +02:00
|
|
|
<refmeta>
|
2002-04-21 21:02:39 +02:00
|
|
|
<refentrytitle>pg_restore</refentrytitle>
|
2000-12-26 00:15:27 +01:00
|
|
|
<manvolnum>1</manvolnum>
|
2000-10-12 16:09:37 +02:00
|
|
|
<refmiscinfo>Application</refmiscinfo>
|
|
|
|
</refmeta>
|
2001-03-06 19:55:57 +01:00
|
|
|
|
2000-10-12 16:09:37 +02:00
|
|
|
<refnamediv>
|
2001-03-06 19:55:57 +01:00
|
|
|
<refname>pg_restore</refname>
|
|
|
|
|
2000-10-12 16:09:37 +02:00
|
|
|
<refpurpose>
|
2007-05-15 21:13:55 +02:00
|
|
|
restore a <productname>PostgreSQL</productname> database from an
|
|
|
|
archive file created by <application>pg_dump</application>
|
2000-10-12 16:09:37 +02:00
|
|
|
</refpurpose>
|
|
|
|
</refnamediv>
|
2001-03-06 19:55:57 +01:00
|
|
|
|
2000-10-12 16:09:37 +02:00
|
|
|
<refsynopsisdiv>
|
2001-03-06 19:55:57 +01:00
|
|
|
<cmdsynopsis>
|
|
|
|
<command>pg_restore</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>
|
2012-05-03 21:50:04 +02:00
|
|
|
<arg choice="opt"><replaceable>filename</replaceable></arg>
|
2001-03-06 19:55:57 +01:00
|
|
|
</cmdsynopsis>
|
|
|
|
</refsynopsisdiv>
|
|
|
|
|
|
|
|
|
|
|
|
<refsect1 id="app-pgrestore-description">
|
2002-10-12 01:03:48 +02:00
|
|
|
<title>Description</title>
|
2001-03-06 19:55:57 +01:00
|
|
|
|
|
|
|
<para>
|
2002-10-12 01:03:48 +02:00
|
|
|
<application>pg_restore</application> is a utility for restoring a
|
2001-11-28 21:49:10 +01:00
|
|
|
<productname>PostgreSQL</productname> database from an archive
|
2001-08-22 22:23:24 +02:00
|
|
|
created by <xref linkend="app-pgdump"> in one of the non-plain-text
|
2003-03-24 15:32:51 +01:00
|
|
|
formats. It will issue the commands necessary to reconstruct the
|
|
|
|
database to the state it was in at the time it was saved. The
|
|
|
|
archive files also allow <application>pg_restore</application> to
|
|
|
|
be selective about what is restored, or even to reorder the items
|
|
|
|
prior to being restored. The archive files are designed to be
|
|
|
|
portable across architectures.
|
2001-03-06 19:55:57 +01:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2005-06-21 22:45:44 +02:00
|
|
|
<application>pg_restore</application> can operate in two modes.
|
2010-05-15 20:11:07 +02:00
|
|
|
If a database name is specified, <application>pg_restore</application>
|
|
|
|
connects to that database and restores archive contents directly into
|
2005-06-21 22:45:44 +02:00
|
|
|
the database. Otherwise, a script containing the SQL
|
|
|
|
commands necessary to rebuild the database is created and written
|
2010-05-15 20:11:07 +02:00
|
|
|
to a file or standard output. This script output is equivalent to
|
2005-06-21 22:45:44 +02:00
|
|
|
the plain text output format of <application>pg_dump</application>.
|
|
|
|
Some of the options controlling the output are therefore analogous to
|
2002-10-12 01:03:48 +02:00
|
|
|
<application>pg_dump</application> options.
|
2001-03-06 19:55:57 +01:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2002-10-12 01:03:48 +02:00
|
|
|
Obviously, <application>pg_restore</application> cannot restore information
|
2003-03-24 15:32:51 +01:00
|
|
|
that is not present in the archive file. For instance, if the
|
2001-08-22 22:23:24 +02:00
|
|
|
archive was made using the <quote>dump data as
|
2003-03-24 15:32:51 +01:00
|
|
|
<command>INSERT</command> commands</quote> option,
|
2002-10-12 01:03:48 +02:00
|
|
|
<application>pg_restore</application> will not be able to load the data
|
2001-08-22 22:23:24 +02:00
|
|
|
using <command>COPY</command> statements.
|
2001-03-06 19:55:57 +01:00
|
|
|
</para>
|
2002-10-12 01:03:48 +02:00
|
|
|
</refsect1>
|
2001-03-06 19:55:57 +01:00
|
|
|
|
2002-10-12 01:03:48 +02:00
|
|
|
<refsect1 id="app-pgrestore-options">
|
|
|
|
<title>Options</title>
|
2001-03-06 19:55:57 +01:00
|
|
|
|
2000-10-12 16:09:37 +02:00
|
|
|
<para>
|
2003-03-24 15:32:51 +01:00
|
|
|
<application>pg_restore</application> accepts the following command
|
2003-01-06 19:53:25 +01:00
|
|
|
line arguments.
|
2000-10-12 16:09:37 +02:00
|
|
|
|
|
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
2003-03-24 15:32:51 +01:00
|
|
|
<term><replaceable class="parameter">filename</replaceable></term>
|
2000-10-12 16:09:37 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2011-01-23 22:10:15 +01:00
|
|
|
Specifies the location of the archive file (or directory, for a
|
|
|
|
directory-format archive) to be restored.
|
2001-11-27 00:09:21 +01:00
|
|
|
If not specified, the standard input is used.
|
2000-10-12 16:09:37 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2002-03-22 20:20:45 +01:00
|
|
|
<term><option>-a</option></term>
|
|
|
|
<term><option>--data-only</option></term>
|
2000-10-12 16:09:37 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2005-01-04 04:58:16 +01:00
|
|
|
Restore only the data, not the schema (data definitions).
|
Rewrite --section option to decouple it from --schema-only/--data-only.
The initial implementation of pg_dump's --section option supposed that the
existing --schema-only and --data-only options could be made equivalent to
--section settings. This is wrong, though, due to dubious but long since
set-in-stone decisions about where to dump SEQUENCE SET items, as seen in
bug report from Martin Pitt. (And I'm not totally convinced there weren't
other bugs, either.) Undo that coupling and instead drive --section
filtering off current-section state tracked as we scan through the TOC
list to call _tocEntryRequired().
To make sure those decisions don't shift around and hopefully save a few
cycles, run _tocEntryRequired() only once per TOC entry and save the result
in a new TOC field. This required minor rejiggering of ACL handling but
also allows a far cleaner implementation of inhibit_data_for_failed_table.
Also, to ensure that pg_dump and pg_restore have the same behavior with
respect to the --section switches, add _tocEntryRequired() filtering to
WriteToc() and WriteDataChunks(), rather than trying to implement section
filtering in an entirely orthogonal way in dumpDumpableObject(). This
required adjusting the handling of the special ENCODING and STDSTRINGS
items, but they were pretty weird before anyway.
Minor other code review for the patch, too.
2012-05-30 05:22:14 +02:00
|
|
|
Table data, large objects, and sequence values are restored,
|
|
|
|
if present in the archive.
|
2000-10-12 16:09:37 +02:00
|
|
|
</para>
|
Rewrite --section option to decouple it from --schema-only/--data-only.
The initial implementation of pg_dump's --section option supposed that the
existing --schema-only and --data-only options could be made equivalent to
--section settings. This is wrong, though, due to dubious but long since
set-in-stone decisions about where to dump SEQUENCE SET items, as seen in
bug report from Martin Pitt. (And I'm not totally convinced there weren't
other bugs, either.) Undo that coupling and instead drive --section
filtering off current-section state tracked as we scan through the TOC
list to call _tocEntryRequired().
To make sure those decisions don't shift around and hopefully save a few
cycles, run _tocEntryRequired() only once per TOC entry and save the result
in a new TOC field. This required minor rejiggering of ACL handling but
also allows a far cleaner implementation of inhibit_data_for_failed_table.
Also, to ensure that pg_dump and pg_restore have the same behavior with
respect to the --section switches, add _tocEntryRequired() filtering to
WriteToc() and WriteDataChunks(), rather than trying to implement section
filtering in an entirely orthogonal way in dumpDumpableObject(). This
required adjusting the handling of the special ENCODING and STDSTRINGS
items, but they were pretty weird before anyway.
Minor other code review for the patch, too.
2012-05-30 05:22:14 +02:00
|
|
|
|
2011-12-17 01:09:38 +01:00
|
|
|
<para>
|
Rewrite --section option to decouple it from --schema-only/--data-only.
The initial implementation of pg_dump's --section option supposed that the
existing --schema-only and --data-only options could be made equivalent to
--section settings. This is wrong, though, due to dubious but long since
set-in-stone decisions about where to dump SEQUENCE SET items, as seen in
bug report from Martin Pitt. (And I'm not totally convinced there weren't
other bugs, either.) Undo that coupling and instead drive --section
filtering off current-section state tracked as we scan through the TOC
list to call _tocEntryRequired().
To make sure those decisions don't shift around and hopefully save a few
cycles, run _tocEntryRequired() only once per TOC entry and save the result
in a new TOC field. This required minor rejiggering of ACL handling but
also allows a far cleaner implementation of inhibit_data_for_failed_table.
Also, to ensure that pg_dump and pg_restore have the same behavior with
respect to the --section switches, add _tocEntryRequired() filtering to
WriteToc() and WriteDataChunks(), rather than trying to implement section
filtering in an entirely orthogonal way in dumpDumpableObject(). This
required adjusting the handling of the special ENCODING and STDSTRINGS
items, but they were pretty weird before anyway.
Minor other code review for the patch, too.
2012-05-30 05:22:14 +02:00
|
|
|
This option is similar to, but for historical reasons not identical
|
2017-10-09 03:44:17 +02:00
|
|
|
to, specifying <option>--section=data</option>.
|
2011-12-17 01:09:38 +01:00
|
|
|
</para>
|
2000-10-12 16:09:37 +02:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2000-10-20 15:44:39 +02:00
|
|
|
<varlistentry>
|
2002-03-22 20:20:45 +01:00
|
|
|
<term><option>-c</option></term>
|
|
|
|
<term><option>--clean</option></term>
|
2000-10-20 15:44:39 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2005-01-04 04:58:16 +01:00
|
|
|
Clean (drop) database objects before recreating them.
|
2017-10-09 03:44:17 +02:00
|
|
|
(Unless <option>--if-exists</option> is used,
|
2014-03-03 19:02:18 +01:00
|
|
|
this might generate some harmless error messages, if any objects
|
2012-10-20 22:58:32 +02:00
|
|
|
were not present in the destination database.)
|
2000-10-20 15:44:39 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2002-03-22 20:20:45 +01:00
|
|
|
<term><option>-C</option></term>
|
|
|
|
<term><option>--create</option></term>
|
2000-10-20 15:44:39 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2012-10-20 22:58:32 +02:00
|
|
|
Create the database before restoring into it.
|
|
|
|
If <option>--clean</option> is also specified, drop and
|
|
|
|
recreate the target database before connecting to it.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
When this option is used, the database named with <option>-d</option>
|
2017-10-09 03:44:17 +02:00
|
|
|
is used only to issue the initial <command>DROP DATABASE</command> and
|
|
|
|
<command>CREATE DATABASE</command> commands. All data is restored into the
|
2012-10-20 22:58:32 +02:00
|
|
|
database name that appears in the archive.
|
2000-10-20 15:44:39 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2000-10-12 16:09:37 +02:00
|
|
|
<varlistentry>
|
2002-03-22 20:20:45 +01:00
|
|
|
<term><option>-d <replaceable class="parameter">dbname</replaceable></option></term>
|
|
|
|
<term><option>--dbname=<replaceable class="parameter">dbname</replaceable></option></term>
|
2000-10-12 16:09:37 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2002-10-12 01:03:48 +02:00
|
|
|
Connect to database <replaceable
|
|
|
|
class="parameter">dbname</replaceable> and restore directly
|
2003-03-24 15:32:51 +01:00
|
|
|
into the database.
|
2000-10-20 15:44:39 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2004-08-20 06:20:23 +02:00
|
|
|
<varlistentry>
|
|
|
|
<term><option>-e</option></term>
|
|
|
|
<term><option>--exit-on-error</option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Exit if an error is encountered while sending SQL commands to
|
2009-01-05 17:54:37 +01:00
|
|
|
the database. The default is to continue and to display a count of
|
2004-08-20 06:20:23 +02:00
|
|
|
errors at the end of the restoration.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2000-10-20 15:44:39 +02:00
|
|
|
<varlistentry>
|
2002-03-22 20:20:45 +01:00
|
|
|
<term><option>-f <replaceable>filename</replaceable></option></term>
|
|
|
|
<term><option>--file=<replaceable>filename</replaceable></option></term>
|
2000-10-20 15:44:39 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2001-10-24 00:11:22 +02:00
|
|
|
Specify output file for generated script, or for the listing
|
2002-10-12 01:03:48 +02:00
|
|
|
when used with <option>-l</option>. Default is the standard
|
|
|
|
output.
|
2000-10-20 15:44:39 +02: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>
|
2000-10-20 15:44:39 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2005-01-04 04:58:16 +01:00
|
|
|
Specify format of the archive. It is not necessary to specify
|
|
|
|
the format, since <application>pg_restore</application> will
|
|
|
|
determine the format automatically. If specified, it can be
|
|
|
|
one of the following:
|
2000-10-20 15:44:39 +02:00
|
|
|
|
|
|
|
<variablelist>
|
2011-01-23 22:10:15 +01:00
|
|
|
<varlistentry>
|
2017-10-09 03:44:17 +02:00
|
|
|
<term><literal>c</literal></term>
|
|
|
|
<term><literal>custom</literal></term>
|
2011-01-23 22:10:15 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2011-05-25 20:53:26 +02:00
|
|
|
The archive is in the custom format of
|
|
|
|
<application>pg_dump</application>.
|
2011-01-23 22:10:15 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2000-10-20 15:44:39 +02:00
|
|
|
<varlistentry>
|
2017-10-09 03:44:17 +02:00
|
|
|
<term><literal>d</literal></term>
|
|
|
|
<term><literal>directory</literal></term>
|
2000-10-20 15:44:39 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2011-05-25 20:53:26 +02:00
|
|
|
The archive is a directory archive.
|
2000-10-20 15:44:39 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2017-10-09 03:44:17 +02:00
|
|
|
<term><literal>t</literal></term>
|
|
|
|
<term><literal>tar</literal></term>
|
2000-10-20 15:44:39 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2011-05-25 20:53:26 +02:00
|
|
|
The archive is a <command>tar</command> archive.
|
2000-10-20 15:44:39 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2011-08-07 09:49:45 +02:00
|
|
|
</variablelist></para>
|
2000-10-20 15:44:39 +02:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2002-07-13 02:55:53 +02:00
|
|
|
<varlistentry>
|
|
|
|
<term><option>-I <replaceable class="parameter">index</replaceable></option></term>
|
|
|
|
<term><option>--index=<replaceable class="parameter">index</replaceable></option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
2013-08-28 08:43:34 +02:00
|
|
|
Restore definition of named index only. Multiple indexes
|
2017-10-09 03:44:17 +02:00
|
|
|
may be specified with multiple <option>-I</option> switches.
|
2002-07-13 02:55:53 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2009-03-20 10:21:09 +01:00
|
|
|
<varlistentry>
|
|
|
|
<term><option>-j <replaceable class="parameter">number-of-jobs</replaceable></option></term>
|
|
|
|
<term><option>--jobs=<replaceable class="parameter">number-of-jobs</replaceable></option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Run the most time-consuming parts
|
2017-10-09 03:44:17 +02:00
|
|
|
of <application>pg_restore</application> — those which load data,
|
2009-03-20 10:21:09 +01:00
|
|
|
create indexes, or create constraints — using multiple
|
|
|
|
concurrent jobs. This option can dramatically reduce the time
|
|
|
|
to restore a large database to a server running on a
|
2010-08-17 06:37:21 +02:00
|
|
|
multiprocessor machine.
|
2009-03-20 10:21:09 +01:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
Each job is one process or one thread, depending on the
|
|
|
|
operating system, and uses a separate connection to the
|
|
|
|
server.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
The optimal value for this option depends on the hardware
|
|
|
|
setup of the server, of the client, and of the network.
|
|
|
|
Factors include the number of CPU cores and the disk setup. A
|
|
|
|
good place to start is the number of CPU cores on the server,
|
|
|
|
but values larger than that can also lead to faster restore
|
|
|
|
times in many cases. Of course, values that are too high will
|
2010-02-19 04:50:03 +01:00
|
|
|
lead to decreased performance because of thrashing.
|
2009-03-20 10:21:09 +01:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2013-06-16 02:38:18 +02:00
|
|
|
Only the custom and directory archive formats are supported
|
|
|
|
with this option.
|
|
|
|
The input must be a regular file or directory (not, for example, a
|
2009-03-20 10:21:09 +01:00
|
|
|
pipe). This option is ignored when emitting a script rather
|
|
|
|
than connecting directly to a database server. Also, multiple
|
|
|
|
jobs cannot be used together with the
|
|
|
|
option <option>--single-transaction</option>.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2000-10-20 15:44:39 +02:00
|
|
|
<varlistentry>
|
2002-03-22 20:20:45 +01:00
|
|
|
<term><option>-l</option></term>
|
|
|
|
<term><option>--list</option></term>
|
2000-10-20 15:44:39 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2017-08-11 21:52:39 +02:00
|
|
|
List the table of contents of the archive. The output of this operation
|
2010-05-15 20:11:07 +02:00
|
|
|
can be used as input to the <option>-L</option> option. Note that
|
2017-10-09 03:44:17 +02:00
|
|
|
if filtering switches such as <option>-n</option> or <option>-t</option> are
|
|
|
|
used with <option>-l</option>, they will restrict the items listed.
|
2000-10-12 16:09:37 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2001-03-06 06:22:50 +01:00
|
|
|
<varlistentry>
|
2002-03-22 20:20:45 +01:00
|
|
|
<term><option>-L <replaceable class="parameter">list-file</replaceable></option></term>
|
|
|
|
<term><option>--use-list=<replaceable class="parameter">list-file</replaceable></option></term>
|
2001-03-06 06:22:50 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2010-05-15 20:11:07 +02:00
|
|
|
Restore only those archive elements that are listed in <replaceable
|
2017-10-09 04:00:57 +02:00
|
|
|
class="parameter">list-file</replaceable>, and restore them in the
|
2010-05-15 20:11:07 +02:00
|
|
|
order they appear in the file. Note that
|
2017-10-09 03:44:17 +02:00
|
|
|
if filtering switches such as <option>-n</option> or <option>-t</option> are
|
|
|
|
used with <option>-L</option>, they will further restrict the items restored.
|
2010-05-15 20:11:07 +02:00
|
|
|
</para>
|
2017-10-09 03:44:17 +02:00
|
|
|
<para><replaceable class="parameter">list-file</replaceable> is normally created by
|
|
|
|
editing the output of a previous <option>-l</option> operation.
|
2010-05-15 20:11:07 +02:00
|
|
|
Lines can be moved or removed, and can also
|
|
|
|
be commented out by placing a semicolon (<literal>;</literal>) at the
|
|
|
|
start of the line. See below for examples.
|
2001-03-06 06:22:50 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2009-02-02 21:07:37 +01:00
|
|
|
<varlistentry>
|
2016-09-20 18:00:00 +02:00
|
|
|
<term><option>-n <replaceable class="parameter">schema</replaceable></option></term>
|
2005-06-09 19:56:51 +02:00
|
|
|
<term><option>--schema=<replaceable class="parameter">schema</replaceable></option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
2013-08-28 08:43:34 +02:00
|
|
|
Restore only objects that are in the named schema. Multiple schemas
|
2017-10-09 03:44:17 +02:00
|
|
|
may be specified with multiple <option>-n</option> switches. This can be
|
2005-11-01 22:09:51 +01:00
|
|
|
combined with the <option>-t</option> option to restore just a
|
|
|
|
specific table.
|
2005-06-09 19:56:51 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2016-09-20 18:00:00 +02:00
|
|
|
<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 restore objects that are in the named schema. Multiple schemas
|
2017-10-09 03:44:17 +02:00
|
|
|
to be excluded may be specified with multiple <option>-N</option> switches.
|
2016-09-20 18:00:00 +02:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2017-10-09 03:44:17 +02:00
|
|
|
When both <option>-n</option> and <option>-N</option> are given for the same
|
|
|
|
schema name, the <option>-N</option> switch wins and the schema is excluded.
|
2016-09-20 18:00:00 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2000-10-12 16:09:37 +02:00
|
|
|
<varlistentry>
|
2002-03-22 20:20:45 +01:00
|
|
|
<term><option>-O</option></term>
|
|
|
|
<term><option>--no-owner</option></term>
|
2000-10-12 16:09:37 +02: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_restore</application> issues
|
2017-10-09 03:44:17 +02:00
|
|
|
<command>ALTER OWNER</command> or
|
2005-01-04 04:58:16 +01:00
|
|
|
<command>SET SESSION AUTHORIZATION</command>
|
|
|
|
statements to set ownership of created schema elements.
|
|
|
|
These statements will fail unless the initial connection to the
|
|
|
|
database is made by a superuser
|
|
|
|
(or the same user that owns all of the objects in the script).
|
|
|
|
With <option>-O</option>, any user name can be used for the
|
|
|
|
initial connection, and this user will own all the created objects.
|
2000-10-20 15:44:39 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2002-07-04 05:04:55 +02:00
|
|
|
<term><option>-P <replaceable class="parameter">function-name(argtype [, ...])</replaceable></option></term>
|
|
|
|
<term><option>--function=<replaceable class="parameter">function-name(argtype [, ...])</replaceable></option></term>
|
2000-10-20 15:44:39 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2003-06-11 18:29:42 +02:00
|
|
|
Restore the named function only. Be careful to spell the function
|
2005-01-04 04:58:16 +01:00
|
|
|
name and arguments exactly as they appear in the dump file's table
|
2013-08-28 08:43:34 +02:00
|
|
|
of contents. Multiple functions may be specified with multiple
|
2017-10-09 03:44:17 +02:00
|
|
|
<option>-P</option> switches.
|
2000-10-20 15:44:39 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2002-03-22 20:20:45 +01:00
|
|
|
<term><option>-R</option></term>
|
|
|
|
<term><option>--no-reconnect</option></term>
|
2000-10-20 15:44:39 +02: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.
|
2000-10-20 15:44:39 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2002-03-22 20:20:45 +01:00
|
|
|
<term><option>-s</option></term>
|
|
|
|
<term><option>--schema-only</option></term>
|
2000-10-20 15:44:39 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
Rewrite --section option to decouple it from --schema-only/--data-only.
The initial implementation of pg_dump's --section option supposed that the
existing --schema-only and --data-only options could be made equivalent to
--section settings. This is wrong, though, due to dubious but long since
set-in-stone decisions about where to dump SEQUENCE SET items, as seen in
bug report from Martin Pitt. (And I'm not totally convinced there weren't
other bugs, either.) Undo that coupling and instead drive --section
filtering off current-section state tracked as we scan through the TOC
list to call _tocEntryRequired().
To make sure those decisions don't shift around and hopefully save a few
cycles, run _tocEntryRequired() only once per TOC entry and save the result
in a new TOC field. This required minor rejiggering of ACL handling but
also allows a far cleaner implementation of inhibit_data_for_failed_table.
Also, to ensure that pg_dump and pg_restore have the same behavior with
respect to the --section switches, add _tocEntryRequired() filtering to
WriteToc() and WriteDataChunks(), rather than trying to implement section
filtering in an entirely orthogonal way in dumpDumpableObject(). This
required adjusting the handling of the special ENCODING and STDSTRINGS
items, but they were pretty weird before anyway.
Minor other code review for the patch, too.
2012-05-30 05:22:14 +02:00
|
|
|
Restore only the schema (data definitions), not data,
|
|
|
|
to the extent that schema entries are present in the archive.
|
2000-10-12 16:09:37 +02:00
|
|
|
</para>
|
2011-12-17 01:09:38 +01:00
|
|
|
<para>
|
2017-10-09 03:44:17 +02:00
|
|
|
This option is the inverse of <option>--data-only</option>.
|
Rewrite --section option to decouple it from --schema-only/--data-only.
The initial implementation of pg_dump's --section option supposed that the
existing --schema-only and --data-only options could be made equivalent to
--section settings. This is wrong, though, due to dubious but long since
set-in-stone decisions about where to dump SEQUENCE SET items, as seen in
bug report from Martin Pitt. (And I'm not totally convinced there weren't
other bugs, either.) Undo that coupling and instead drive --section
filtering off current-section state tracked as we scan through the TOC
list to call _tocEntryRequired().
To make sure those decisions don't shift around and hopefully save a few
cycles, run _tocEntryRequired() only once per TOC entry and save the result
in a new TOC field. This required minor rejiggering of ACL handling but
also allows a far cleaner implementation of inhibit_data_for_failed_table.
Also, to ensure that pg_dump and pg_restore have the same behavior with
respect to the --section switches, add _tocEntryRequired() filtering to
WriteToc() and WriteDataChunks(), rather than trying to implement section
filtering in an entirely orthogonal way in dumpDumpableObject(). This
required adjusting the handling of the special ENCODING and STDSTRINGS
items, but they were pretty weird before anyway.
Minor other code review for the patch, too.
2012-05-30 05:22:14 +02:00
|
|
|
It is similar to, but for historical reasons not identical to,
|
|
|
|
specifying
|
2017-10-09 03:44:17 +02:00
|
|
|
<option>--section=pre-data --section=post-data</option>.
|
2011-12-17 01:09:38 +01:00
|
|
|
</para>
|
Rewrite --section option to decouple it from --schema-only/--data-only.
The initial implementation of pg_dump's --section option supposed that the
existing --schema-only and --data-only options could be made equivalent to
--section settings. This is wrong, though, due to dubious but long since
set-in-stone decisions about where to dump SEQUENCE SET items, as seen in
bug report from Martin Pitt. (And I'm not totally convinced there weren't
other bugs, either.) Undo that coupling and instead drive --section
filtering off current-section state tracked as we scan through the TOC
list to call _tocEntryRequired().
To make sure those decisions don't shift around and hopefully save a few
cycles, run _tocEntryRequired() only once per TOC entry and save the result
in a new TOC field. This required minor rejiggering of ACL handling but
also allows a far cleaner implementation of inhibit_data_for_failed_table.
Also, to ensure that pg_dump and pg_restore have the same behavior with
respect to the --section switches, add _tocEntryRequired() filtering to
WriteToc() and WriteDataChunks(), rather than trying to implement section
filtering in an entirely orthogonal way in dumpDumpableObject(). This
required adjusting the handling of the special ENCODING and STDSTRINGS
items, but they were pretty weird before anyway.
Minor other code review for the patch, too.
2012-05-30 05:22:14 +02:00
|
|
|
<para>
|
2017-10-09 03:44:17 +02:00
|
|
|
(Do not confuse this with the <option>--schema</option> option, which
|
|
|
|
uses the word <quote>schema</quote> in a different meaning.)
|
Rewrite --section option to decouple it from --schema-only/--data-only.
The initial implementation of pg_dump's --section option supposed that the
existing --schema-only and --data-only options could be made equivalent to
--section settings. This is wrong, though, due to dubious but long since
set-in-stone decisions about where to dump SEQUENCE SET items, as seen in
bug report from Martin Pitt. (And I'm not totally convinced there weren't
other bugs, either.) Undo that coupling and instead drive --section
filtering off current-section state tracked as we scan through the TOC
list to call _tocEntryRequired().
To make sure those decisions don't shift around and hopefully save a few
cycles, run _tocEntryRequired() only once per TOC entry and save the result
in a new TOC field. This required minor rejiggering of ACL handling but
also allows a far cleaner implementation of inhibit_data_for_failed_table.
Also, to ensure that pg_dump and pg_restore have the same behavior with
respect to the --section switches, add _tocEntryRequired() filtering to
WriteToc() and WriteDataChunks(), rather than trying to implement section
filtering in an entirely orthogonal way in dumpDumpableObject(). This
required adjusting the handling of the special ENCODING and STDSTRINGS
items, but they were pretty weird before anyway.
Minor other code review for the patch, too.
2012-05-30 05:22:14 +02:00
|
|
|
</para>
|
2000-10-12 16:09:37 +02:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2000-10-20 15:44:39 +02: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>
|
2000-10-20 15:44:39 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2002-05-11 00:36:27 +02:00
|
|
|
Specify the superuser user name to use when disabling triggers.
|
2017-10-09 03:44:17 +02:00
|
|
|
This is relevant only if <option>--disable-triggers</option> is used.
|
2000-10-20 15:44:39 +02: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>
|
2000-10-20 15:44:39 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2015-07-03 00:13:34 +02:00
|
|
|
Restore definition and/or data of only the named table.
|
2017-10-09 03:44:17 +02:00
|
|
|
For this purpose, <quote>table</quote> includes views, materialized views,
|
2015-07-03 00:13:34 +02:00
|
|
|
sequences, and foreign tables. Multiple tables
|
2017-10-09 03:44:17 +02:00
|
|
|
can be selected by writing multiple <option>-t</option> switches.
|
2015-07-03 00:13:34 +02:00
|
|
|
This option can be combined with the <option>-n</option> option to
|
|
|
|
specify table(s) in a particular schema.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<note>
|
|
|
|
<para>
|
2017-10-09 03:44:17 +02:00
|
|
|
When <option>-t</option> is specified, <application>pg_restore</application>
|
2015-07-03 00:13:34 +02:00
|
|
|
makes no attempt to restore any other database objects that the
|
|
|
|
selected table(s) might depend upon. Therefore, there is no
|
|
|
|
guarantee that a specific-table restore into a clean database will
|
|
|
|
succeed.
|
|
|
|
</para>
|
|
|
|
</note>
|
|
|
|
|
|
|
|
<note>
|
|
|
|
<para>
|
|
|
|
This flag does not behave identically to the <option>-t</option>
|
|
|
|
flag of <application>pg_dump</application>. There is not currently
|
2017-10-09 03:44:17 +02:00
|
|
|
any provision for wild-card matching in <application>pg_restore</application>,
|
|
|
|
nor can you include a schema name within its <option>-t</option>.
|
2015-07-03 00:13:34 +02:00
|
|
|
</para>
|
|
|
|
</note>
|
|
|
|
|
|
|
|
<note>
|
|
|
|
<para>
|
2017-10-09 03:44:17 +02:00
|
|
|
In versions prior to <productname>PostgreSQL</productname> 9.6, this flag
|
2015-07-03 00:13:34 +02:00
|
|
|
matched only tables, not any other type of relation.
|
|
|
|
</para>
|
|
|
|
</note>
|
2000-10-20 15:44:39 +02:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2002-03-22 20:20:45 +01:00
|
|
|
<term><option>-T <replaceable class="parameter">trigger</replaceable></option></term>
|
|
|
|
<term><option>--trigger=<replaceable class="parameter">trigger</replaceable></option></term>
|
2000-10-20 15:44:39 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2013-08-28 08:43:34 +02:00
|
|
|
Restore named trigger only. Multiple triggers may be specified with
|
2017-10-09 03:44:17 +02:00
|
|
|
multiple <option>-T</option> switches.
|
2000-10-20 15:44:39 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2000-10-12 16:09:37 +02:00
|
|
|
<varlistentry>
|
2002-03-22 20:20:45 +01:00
|
|
|
<term><option>-v</option></term>
|
|
|
|
<term><option>--verbose</option></term>
|
2000-10-12 16:09:37 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2005-01-04 04:58:16 +01:00
|
|
|
Specifies verbose mode.
|
2000-10-12 16:09:37 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2010-02-19 15:36:45 +01:00
|
|
|
<varlistentry>
|
2017-10-09 03:44:17 +02:00
|
|
|
<term><option>-V</option></term>
|
|
|
|
<term><option>--version</option></term>
|
2010-02-19 15:36:45 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Print the <application>pg_restore</application> version and exit.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2000-10-12 16:09:37 +02:00
|
|
|
<varlistentry>
|
2002-03-22 20:20:45 +01:00
|
|
|
<term><option>-x</option></term>
|
|
|
|
<term><option>--no-privileges</option></term>
|
|
|
|
<term><option>--no-acl</option></term>
|
2000-10-12 16:09:37 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2005-01-04 04:58:16 +01:00
|
|
|
Prevent restoration of access privileges (grant/revoke commands).
|
2000-10-12 16:09:37 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2011-05-25 20:53:26 +02:00
|
|
|
<varlistentry>
|
|
|
|
<term><option>-1</option></term>
|
|
|
|
<term><option>--single-transaction</option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Execute the restore as a single transaction (that is, wrap the
|
2017-10-09 03:44:17 +02:00
|
|
|
emitted commands in <command>BEGIN</command>/<command>COMMIT</command>). This
|
2011-05-25 20:53:26 +02:00
|
|
|
ensures that either all the commands complete successfully, or no
|
|
|
|
changes are applied. This option implies
|
2017-10-09 03:44:17 +02:00
|
|
|
<option>--exit-on-error</option>.
|
2011-05-25 20:53:26 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2002-05-11 00:36:27 +02:00
|
|
|
<varlistentry>
|
2017-10-09 03:44:17 +02:00
|
|
|
<term><option>--disable-triggers</option></term>
|
2002-05-11 00:36:27 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2012-11-12 04:50:24 +01:00
|
|
|
This option is relevant only when performing a data-only restore.
|
2005-01-04 04:58:16 +01:00
|
|
|
It instructs <application>pg_restore</application> to execute 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>
|
2002-11-15 04:11:18 +01:00
|
|
|
Presently, the commands emitted for
|
2017-10-09 03:44:17 +02:00
|
|
|
<option>--disable-triggers</option> must be done as superuser. So you
|
|
|
|
should also specify a superuser name with <option>-S</option> or,
|
2012-11-15 06:04:23 +01:00
|
|
|
preferably, run <application>pg_restore</application> as a
|
2017-10-09 03:44:17 +02:00
|
|
|
<productname>PostgreSQL</productname> superuser.
|
2002-05-11 00:36:27 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
Code review for row security.
Buildfarm member tick identified an issue where the policies in the
relcache for a relation were were being replaced underneath a running
query, leading to segfaults while processing the policies to be added
to a query. Similar to how TupleDesc RuleLocks are handled, add in a
equalRSDesc() function to check if the policies have actually changed
and, if not, swap back the rsdesc field (using the original instead of
the temporairly built one; the whole structure is swapped and then
specific fields swapped back). This now passes a CLOBBER_CACHE_ALWAYS
for me and should resolve the buildfarm error.
In addition to addressing this, add a new chapter in Data Definition
under Privileges which explains row security and provides examples of
its usage, change \d to always list policies (even if row security is
disabled- but note that it is disabled, or enabled with no policies),
rework check_role_for_policy (it really didn't need the entire policy,
but it did need to be using has_privs_of_role()), and change the field
in pg_class to relrowsecurity from relhasrowsecurity, based on
Heikki's suggestion. Also from Heikki, only issue SET ROW_SECURITY in
pg_restore when talking to a 9.5+ server, list Bypass RLS in \du, and
document --enable-row-security options for pg_dump and pg_restore.
Lastly, fix a number of minor whitespace and typo issues from Heikki,
Dimitri, add a missing #include, per Peter E, fix a few minor
variable-assigned-but-not-used and resource leak issues from Coverity
and add tab completion for role attribute bypassrls as well.
2014-09-24 22:32:22 +02:00
|
|
|
<varlistentry>
|
2017-10-09 03:44:17 +02:00
|
|
|
<term><option>--enable-row-security</option></term>
|
2015-09-18 02:56:58 +02:00
|
|
|
<listitem>
|
Code review for row security.
Buildfarm member tick identified an issue where the policies in the
relcache for a relation were were being replaced underneath a running
query, leading to segfaults while processing the policies to be added
to a query. Similar to how TupleDesc RuleLocks are handled, add in a
equalRSDesc() function to check if the policies have actually changed
and, if not, swap back the rsdesc field (using the original instead of
the temporairly built one; the whole structure is swapped and then
specific fields swapped back). This now passes a CLOBBER_CACHE_ALWAYS
for me and should resolve the buildfarm error.
In addition to addressing this, add a new chapter in Data Definition
under Privileges which explains row security and provides examples of
its usage, change \d to always list policies (even if row security is
disabled- but note that it is disabled, or enabled with no policies),
rework check_role_for_policy (it really didn't need the entire policy,
but it did need to be using has_privs_of_role()), and change the field
in pg_class to relrowsecurity from relhasrowsecurity, based on
Heikki's suggestion. Also from Heikki, only issue SET ROW_SECURITY in
pg_restore when talking to a 9.5+ server, list Bypass RLS in \du, and
document --enable-row-security options for pg_dump and pg_restore.
Lastly, fix a number of minor whitespace and typo issues from Heikki,
Dimitri, add a missing #include, per Peter E, fix a few minor
variable-assigned-but-not-used and resource leak issues from Coverity
and add tab completion for role attribute bypassrls as well.
2014-09-24 22:32:22 +02:00
|
|
|
<para>
|
|
|
|
This option is relevant only when restoring the contents of a table
|
2015-09-18 02:56:58 +02:00
|
|
|
which has row security. By default, <application>pg_restore</application> will set
|
|
|
|
<xref linkend="guc-row-security"> to off, to ensure
|
Code review for row security.
Buildfarm member tick identified an issue where the policies in the
relcache for a relation were were being replaced underneath a running
query, leading to segfaults while processing the policies to be added
to a query. Similar to how TupleDesc RuleLocks are handled, add in a
equalRSDesc() function to check if the policies have actually changed
and, if not, swap back the rsdesc field (using the original instead of
the temporairly built one; the whole structure is swapped and then
specific fields swapped back). This now passes a CLOBBER_CACHE_ALWAYS
for me and should resolve the buildfarm error.
In addition to addressing this, add a new chapter in Data Definition
under Privileges which explains row security and provides examples of
its usage, change \d to always list policies (even if row security is
disabled- but note that it is disabled, or enabled with no policies),
rework check_role_for_policy (it really didn't need the entire policy,
but it did need to be using has_privs_of_role()), and change the field
in pg_class to relrowsecurity from relhasrowsecurity, based on
Heikki's suggestion. Also from Heikki, only issue SET ROW_SECURITY in
pg_restore when talking to a 9.5+ server, list Bypass RLS in \du, and
document --enable-row-security options for pg_dump and pg_restore.
Lastly, fix a number of minor whitespace and typo issues from Heikki,
Dimitri, add a missing #include, per Peter E, fix a few minor
variable-assigned-but-not-used and resource leak issues from Coverity
and add tab completion for role attribute bypassrls as well.
2014-09-24 22:32:22 +02:00
|
|
|
that all data is restored in to the table. If the user does not have
|
|
|
|
sufficient privileges to bypass row security, then an error is thrown.
|
|
|
|
This parameter instructs <application>pg_restore</application> to set
|
2015-09-18 02:56:58 +02:00
|
|
|
<xref linkend="guc-row-security"> to on instead, allowing the user to attempt to restore
|
|
|
|
the contents of the table with row security enabled. This might still
|
Code review for row security.
Buildfarm member tick identified an issue where the policies in the
relcache for a relation were were being replaced underneath a running
query, leading to segfaults while processing the policies to be added
to a query. Similar to how TupleDesc RuleLocks are handled, add in a
equalRSDesc() function to check if the policies have actually changed
and, if not, swap back the rsdesc field (using the original instead of
the temporairly built one; the whole structure is swapped and then
specific fields swapped back). This now passes a CLOBBER_CACHE_ALWAYS
for me and should resolve the buildfarm error.
In addition to addressing this, add a new chapter in Data Definition
under Privileges which explains row security and provides examples of
its usage, change \d to always list policies (even if row security is
disabled- but note that it is disabled, or enabled with no policies),
rework check_role_for_policy (it really didn't need the entire policy,
but it did need to be using has_privs_of_role()), and change the field
in pg_class to relrowsecurity from relhasrowsecurity, based on
Heikki's suggestion. Also from Heikki, only issue SET ROW_SECURITY in
pg_restore when talking to a 9.5+ server, list Bypass RLS in \du, and
document --enable-row-security options for pg_dump and pg_restore.
Lastly, fix a number of minor whitespace and typo issues from Heikki,
Dimitri, add a missing #include, per Peter E, fix a few minor
variable-assigned-but-not-used and resource leak issues from Coverity
and add tab completion for role attribute bypassrls as well.
2014-09-24 22:32:22 +02:00
|
|
|
fail if the user does not have the right to insert the rows from the
|
|
|
|
dump into the table.
|
|
|
|
</para>
|
2015-07-03 00:13:34 +02:00
|
|
|
|
Code review for row security.
Buildfarm member tick identified an issue where the policies in the
relcache for a relation were were being replaced underneath a running
query, leading to segfaults while processing the policies to be added
to a query. Similar to how TupleDesc RuleLocks are handled, add in a
equalRSDesc() function to check if the policies have actually changed
and, if not, swap back the rsdesc field (using the original instead of
the temporairly built one; the whole structure is swapped and then
specific fields swapped back). This now passes a CLOBBER_CACHE_ALWAYS
for me and should resolve the buildfarm error.
In addition to addressing this, add a new chapter in Data Definition
under Privileges which explains row security and provides examples of
its usage, change \d to always list policies (even if row security is
disabled- but note that it is disabled, or enabled with no policies),
rework check_role_for_policy (it really didn't need the entire policy,
but it did need to be using has_privs_of_role()), and change the field
in pg_class to relrowsecurity from relhasrowsecurity, based on
Heikki's suggestion. Also from Heikki, only issue SET ROW_SECURITY in
pg_restore when talking to a 9.5+ server, list Bypass RLS in \du, and
document --enable-row-security options for pg_dump and pg_restore.
Lastly, fix a number of minor whitespace and typo issues from Heikki,
Dimitri, add a missing #include, per Peter E, fix a few minor
variable-assigned-but-not-used and resource leak issues from Coverity
and add tab completion for role attribute bypassrls as well.
2014-09-24 22:32:22 +02:00
|
|
|
<para>
|
2015-09-18 02:56:58 +02:00
|
|
|
Note that this option currently also requires the dump be in <command>INSERT</command>
|
2016-12-23 02:56:50 +01:00
|
|
|
format, as <command>COPY FROM</command> does not support row security.
|
Code review for row security.
Buildfarm member tick identified an issue where the policies in the
relcache for a relation were were being replaced underneath a running
query, leading to segfaults while processing the policies to be added
to a query. Similar to how TupleDesc RuleLocks are handled, add in a
equalRSDesc() function to check if the policies have actually changed
and, if not, swap back the rsdesc field (using the original instead of
the temporairly built one; the whole structure is swapped and then
specific fields swapped back). This now passes a CLOBBER_CACHE_ALWAYS
for me and should resolve the buildfarm error.
In addition to addressing this, add a new chapter in Data Definition
under Privileges which explains row security and provides examples of
its usage, change \d to always list policies (even if row security is
disabled- but note that it is disabled, or enabled with no policies),
rework check_role_for_policy (it really didn't need the entire policy,
but it did need to be using has_privs_of_role()), and change the field
in pg_class to relrowsecurity from relhasrowsecurity, based on
Heikki's suggestion. Also from Heikki, only issue SET ROW_SECURITY in
pg_restore when talking to a 9.5+ server, list Bypass RLS in \du, and
document --enable-row-security options for pg_dump and pg_restore.
Lastly, fix a number of minor whitespace and typo issues from Heikki,
Dimitri, add a missing #include, per Peter E, fix a few minor
variable-assigned-but-not-used and resource leak issues from Coverity
and add tab completion for role attribute bypassrls as well.
2014-09-24 22:32:22 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2006-08-01 20:21:44 +02:00
|
|
|
<varlistentry>
|
2014-03-03 19:02:18 +01:00
|
|
|
<term><option>--if-exists</option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Use conditional commands (i.e. add an <literal>IF EXISTS</literal>
|
|
|
|
clause) when cleaning database objects. This option is not valid
|
2017-10-09 03:44:17 +02:00
|
|
|
unless <option>--clean</option> is also specified.
|
2014-03-03 19:02:18 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2006-10-15 01:07:22 +02:00
|
|
|
<term><option>--no-data-for-failed-tables</option></term>
|
2006-08-01 20:21:44 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2006-10-15 01:07:22 +02:00
|
|
|
By default, table data is restored even if the creation command
|
|
|
|
for the table failed (e.g., because it already exists).
|
|
|
|
With this option, data for such a table is skipped.
|
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
|
|
|
This behavior is useful if the target database already
|
|
|
|
contains the desired table contents. For example,
|
2017-10-09 03:44:17 +02:00
|
|
|
auxiliary tables for <productname>PostgreSQL</productname> extensions
|
|
|
|
such as <productname>PostGIS</productname> might already be loaded in
|
2006-10-15 01:07:22 +02:00
|
|
|
the target database; specifying this option prevents duplicate
|
|
|
|
or obsolete data from being loaded into them.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
This option is effective only when restoring directly into a
|
|
|
|
database, not when producing SQL script output.
|
2006-08-01 20:21:44 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2017-05-12 15:15:40 +02:00
|
|
|
<varlistentry>
|
|
|
|
<term><option>--no-publications</option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Do not output commands to restore publications, even if the archive
|
|
|
|
contains them.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2009-01-05 17:54:37 +01:00
|
|
|
<varlistentry>
|
2011-05-25 20:53:26 +02:00
|
|
|
<term><option>--no-security-labels</option></term>
|
2009-01-05 17:54:37 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2011-05-25 20:53:26 +02:00
|
|
|
Do not output commands to restore security labels,
|
|
|
|
even if the archive contains them.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2017-05-09 16:58:06 +02:00
|
|
|
<varlistentry>
|
|
|
|
<term><option>--no-subscriptions</option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Do not output commands to restore subscriptions, even if the archive
|
|
|
|
contains them.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2011-05-25 20:53:26 +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>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2011-12-17 01:09:38 +01:00
|
|
|
<varlistentry>
|
|
|
|
<term><option>--section=<replaceable class="parameter">sectionname</replaceable></option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
Rewrite --section option to decouple it from --schema-only/--data-only.
The initial implementation of pg_dump's --section option supposed that the
existing --schema-only and --data-only options could be made equivalent to
--section settings. This is wrong, though, due to dubious but long since
set-in-stone decisions about where to dump SEQUENCE SET items, as seen in
bug report from Martin Pitt. (And I'm not totally convinced there weren't
other bugs, either.) Undo that coupling and instead drive --section
filtering off current-section state tracked as we scan through the TOC
list to call _tocEntryRequired().
To make sure those decisions don't shift around and hopefully save a few
cycles, run _tocEntryRequired() only once per TOC entry and save the result
in a new TOC field. This required minor rejiggering of ACL handling but
also allows a far cleaner implementation of inhibit_data_for_failed_table.
Also, to ensure that pg_dump and pg_restore have the same behavior with
respect to the --section switches, add _tocEntryRequired() filtering to
WriteToc() and WriteDataChunks(), rather than trying to implement section
filtering in an entirely orthogonal way in dumpDumpableObject(). This
required adjusting the handling of the special ENCODING and STDSTRINGS
items, but they were pretty weird before anyway.
Minor other code review for the patch, too.
2012-05-30 05:22:14 +02:00
|
|
|
Only restore the named section. The section name can be
|
2017-10-09 03:44:17 +02:00
|
|
|
<option>pre-data</option>, <option>data</option>, or <option>post-data</option>.
|
Rewrite --section option to decouple it from --schema-only/--data-only.
The initial implementation of pg_dump's --section option supposed that the
existing --schema-only and --data-only options could be made equivalent to
--section settings. This is wrong, though, due to dubious but long since
set-in-stone decisions about where to dump SEQUENCE SET items, as seen in
bug report from Martin Pitt. (And I'm not totally convinced there weren't
other bugs, either.) Undo that coupling and instead drive --section
filtering off current-section state tracked as we scan through the TOC
list to call _tocEntryRequired().
To make sure those decisions don't shift around and hopefully save a few
cycles, run _tocEntryRequired() only once per TOC entry and save the result
in a new TOC field. This required minor rejiggering of ACL handling but
also allows a far cleaner implementation of inhibit_data_for_failed_table.
Also, to ensure that pg_dump and pg_restore have the same behavior with
respect to the --section switches, add _tocEntryRequired() filtering to
WriteToc() and WriteDataChunks(), rather than trying to implement section
filtering in an entirely orthogonal way in dumpDumpableObject(). This
required adjusting the handling of the special ENCODING and STDSTRINGS
items, but they were pretty weird before anyway.
Minor other code review for the patch, too.
2012-05-30 05:22:14 +02:00
|
|
|
This option can be specified more than once to select multiple
|
|
|
|
sections. The default is to restore all sections.
|
2011-12-17 01:09:38 +01:00
|
|
|
</para>
|
|
|
|
<para>
|
Rewrite --section option to decouple it from --schema-only/--data-only.
The initial implementation of pg_dump's --section option supposed that the
existing --schema-only and --data-only options could be made equivalent to
--section settings. This is wrong, though, due to dubious but long since
set-in-stone decisions about where to dump SEQUENCE SET items, as seen in
bug report from Martin Pitt. (And I'm not totally convinced there weren't
other bugs, either.) Undo that coupling and instead drive --section
filtering off current-section state tracked as we scan through the TOC
list to call _tocEntryRequired().
To make sure those decisions don't shift around and hopefully save a few
cycles, run _tocEntryRequired() only once per TOC entry and save the result
in a new TOC field. This required minor rejiggering of ACL handling but
also allows a far cleaner implementation of inhibit_data_for_failed_table.
Also, to ensure that pg_dump and pg_restore have the same behavior with
respect to the --section switches, add _tocEntryRequired() filtering to
WriteToc() and WriteDataChunks(), rather than trying to implement section
filtering in an entirely orthogonal way in dumpDumpableObject(). This
required adjusting the handling of the special ENCODING and STDSTRINGS
items, but they were pretty weird before anyway.
Minor other code review for the patch, too.
2012-05-30 05:22:14 +02:00
|
|
|
The data section contains actual table data as well as large-object
|
|
|
|
definitions.
|
|
|
|
Post-data items consist of definitions of indexes, triggers, rules
|
|
|
|
and constraints other than validated check constraints.
|
|
|
|
Pre-data items consist of all other data definition items.
|
2011-12-17 01:09:38 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2016-07-07 03:09:26 +02:00
|
|
|
<varlistentry>
|
2017-10-09 03:44:17 +02:00
|
|
|
<term><option>--strict-names</option></term>
|
2016-07-07 03:09:26 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Require that each schema
|
|
|
|
(<option>-n</option>/<option>--schema</option>) and table
|
|
|
|
(<option>-t</option>/<option>--table</option>) qualifier match at
|
|
|
|
least one schema/table in the backup file.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2011-05-25 20:53:26 +02:00
|
|
|
<varlistentry>
|
|
|
|
<term><option>--use-set-session-authorization</option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
2017-10-09 03:44:17 +02:00
|
|
|
Output SQL-standard <command>SET SESSION AUTHORIZATION</command> commands
|
|
|
|
instead of <command>ALTER OWNER</command> commands to determine object
|
2011-05-25 20:53:26 +02:00
|
|
|
ownership. This makes the dump more standards-compatible, but
|
|
|
|
depending on the history of the objects in the dump, might not restore
|
|
|
|
properly.
|
2009-01-05 17:54:37 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2010-02-19 15:36:45 +01:00
|
|
|
<varlistentry>
|
2017-10-09 03:44:17 +02:00
|
|
|
<term><option>-?</option></term>
|
|
|
|
<term><option>--help</option></term>
|
2010-02-19 15:36:45 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Show help about <application>pg_restore</application> command line
|
|
|
|
arguments, and exit.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2000-10-12 16:09:37 +02:00
|
|
|
</variablelist>
|
|
|
|
</para>
|
2001-03-06 19:55:57 +01:00
|
|
|
|
2000-10-12 16:09:37 +02:00
|
|
|
<para>
|
2003-03-24 15:32:51 +01:00
|
|
|
<application>pg_restore</application> also accepts
|
2000-10-12 16:09:37 +02:00
|
|
|
the following command line arguments for connection parameters:
|
|
|
|
|
|
|
|
<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>
|
2000-10-12 16:09:37 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2005-01-04 04:58:16 +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.
|
2000-10-12 16:09:37 +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>
|
2000-10-12 16:09:37 +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.
|
2003-03-24 15:32:51 +01:00
|
|
|
</para>
|
2000-10-12 16:09:37 +02:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2001-03-06 19:55:57 +01:00
|
|
|
<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>
|
2001-03-06 19:55:57 +01: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>
|
2017-10-09 03:44:17 +02:00
|
|
|
<term><option>-w</option></term>
|
|
|
|
<term><option>--no-password</option></term>
|
2009-02-26 17:02:39 +01:00
|
|
|
<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_restore</application> to prompt for a
|
2009-01-05 17:54:37 +01: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_restore</application> will automatically prompt
|
|
|
|
for a password if the server demands password authentication.
|
|
|
|
However, <application>pg_restore</application> will waste a
|
|
|
|
connection attempt finding out that the server wants a password.
|
2017-10-09 03:44:17 +02:00
|
|
|
In some cases it is worth typing <option>-W</option> to avoid the extra
|
2007-12-11 20:57:32 +01:00
|
|
|
connection attempt.
|
2001-03-06 19:55:57 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2006-02-12 05:04:32 +01:00
|
|
|
|
|
|
|
<varlistentry>
|
2009-01-05 17:54:37 +01:00
|
|
|
<term><option>--role=<replaceable class="parameter">rolename</replaceable></option></term>
|
2006-02-12 05:04:32 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2009-01-05 17:54:37 +01:00
|
|
|
Specifies a role name to be used to perform the restore.
|
2017-10-09 03:44:17 +02:00
|
|
|
This option causes <application>pg_restore</application> to issue a
|
|
|
|
<command>SET ROLE</command> <replaceable class="parameter">rolename</replaceable>
|
2009-01-05 17:54:37 +01:00
|
|
|
command after connecting to the database. It is useful when the
|
2017-10-09 03:44:17 +02:00
|
|
|
authenticated user (specified by <option>-U</option>) lacks privileges
|
|
|
|
needed by <application>pg_restore</application>, but can switch to a role with
|
2009-01-05 17:54:37 +01:00
|
|
|
the required rights. Some installations have a policy against
|
|
|
|
logging in directly as a superuser, and use of this option allows
|
|
|
|
restores to be performed without violating the policy.
|
2006-02-12 05:04:32 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2000-10-12 16:09:37 +02:00
|
|
|
</variablelist>
|
|
|
|
</para>
|
2001-03-06 19:55:57 +01:00
|
|
|
</refsect1>
|
2000-10-12 16:09:37 +02:00
|
|
|
|
2001-03-06 19:55:57 +01:00
|
|
|
|
2002-07-28 17:22:21 +02:00
|
|
|
<refsect1>
|
|
|
|
<title>Environment</title>
|
|
|
|
|
|
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
|
|
|
<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>
|
|
|
|
<term><envar>PGUSER</envar></term>
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<para>
|
2003-03-24 15:32:51 +01:00
|
|
|
Default connection parameters
|
2002-07-28 17:22:21 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
</variablelist>
|
2007-02-20 19:10:59 +01:00
|
|
|
|
|
|
|
<para>
|
2017-10-09 03:44:17 +02:00
|
|
|
This utility, like most other <productname>PostgreSQL</productname> utilities,
|
|
|
|
also uses the environment variables supported by <application>libpq</application>
|
2012-08-27 21:26:53 +02:00
|
|
|
(see <xref linkend="libpq-envars">). However, it does not read
|
|
|
|
<envar>PGDATABASE</envar> when a database name is not supplied.
|
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-pgrestore-diagnostics">
|
|
|
|
<title>Diagnostics</title>
|
|
|
|
|
2003-03-24 15:32:51 +01:00
|
|
|
<para>
|
|
|
|
When a direct database connection is specified using the
|
|
|
|
<option>-d</option> option, <application>pg_restore</application>
|
|
|
|
internally executes <acronym>SQL</acronym> statements. If you have
|
|
|
|
problems running <application>pg_restore</application>, make sure
|
|
|
|
you are able to select information from the database using, for
|
2007-02-20 19:10:59 +01:00
|
|
|
example, <xref 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>
|
2000-10-12 16:09:37 +02:00
|
|
|
</refsect1>
|
|
|
|
|
2001-03-06 19:55:57 +01:00
|
|
|
|
|
|
|
<refsect1 id="app-pgrestore-notes">
|
2002-10-12 01:03:48 +02:00
|
|
|
<title>Notes</title>
|
2001-03-06 19:55:57 +01:00
|
|
|
|
2002-02-11 01:14:10 +01:00
|
|
|
<para>
|
2002-10-12 01:03:48 +02:00
|
|
|
If your installation has any local additions to the
|
2017-10-09 03:44:17 +02:00
|
|
|
<literal>template1</literal> database, be careful to load the output of
|
2002-10-12 01:03:48 +02:00
|
|
|
<application>pg_restore</application> 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
|
2017-10-09 03:44:17 +02:00
|
|
|
additions, copy from <literal>template0</literal> not <literal>template1</literal>, for example:
|
2002-02-11 01:14:10 +01:00
|
|
|
<programlisting>
|
2003-03-24 15:32:51 +01:00
|
|
|
CREATE DATABASE foo WITH TEMPLATE template0;
|
2002-02-11 01:14:10 +01:00
|
|
|
</programlisting>
|
|
|
|
</para>
|
|
|
|
|
2000-10-12 16:09:37 +02:00
|
|
|
<para>
|
2002-10-12 01:03:48 +02:00
|
|
|
The limitations of <application>pg_restore</application> are detailed below.
|
2000-10-12 16:09:37 +02:00
|
|
|
|
|
|
|
<itemizedlist>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
2003-03-24 15:32:51 +01:00
|
|
|
When restoring data to a pre-existing table and the option
|
2017-10-09 03:44:17 +02:00
|
|
|
<option>--disable-triggers</option> is used,
|
2003-03-24 15:32:51 +01:00
|
|
|
<application>pg_restore</application> emits commands
|
2010-02-19 04:50:03 +01:00
|
|
|
to disable triggers on user tables before inserting the data, then emits commands to
|
2000-10-20 15:44:39 +02:00
|
|
|
re-enable them after the data has been inserted. If the restore is stopped in the
|
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
|
|
|
middle, the system catalogs might be left in the wrong state.
|
2000-10-12 16:09:37 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
<listitem>
|
2011-08-07 09:49:45 +02:00
|
|
|
<para><application>pg_restore</application> cannot restore large objects
|
2010-02-19 04:50:03 +01:00
|
|
|
selectively; for instance, only those for a specific table. If
|
2008-09-07 21:12:57 +02:00
|
|
|
an archive contains large objects, then all large objects will be
|
|
|
|
restored, or none of them if they are excluded via <option>-L</option>,
|
|
|
|
<option>-t</option>, or other options.
|
2000-10-12 16:09:37 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
</itemizedlist>
|
|
|
|
</para>
|
2001-03-06 19:55:57 +01:00
|
|
|
|
|
|
|
<para>
|
2002-10-12 01:03:48 +02:00
|
|
|
See also the <xref linkend="app-pgdump"> documentation for details on
|
|
|
|
limitations of <application>pg_dump</application>.
|
2001-03-06 19:55:57 +01:00
|
|
|
</para>
|
2003-03-18 01:02:11 +01:00
|
|
|
|
|
|
|
<para>
|
2017-10-09 03:44:17 +02:00
|
|
|
Once restored, it is wise to run <command>ANALYZE</command> on each
|
2009-08-07 22:54:31 +02:00
|
|
|
restored table so the optimizer has useful statistics; see
|
|
|
|
<xref linkend="vacuum-for-statistics"> and
|
|
|
|
<xref linkend="autovacuum"> for more information.
|
2003-03-18 01:02:11 +01:00
|
|
|
</para>
|
|
|
|
|
2000-10-12 16:09:37 +02:00
|
|
|
</refsect1>
|
|
|
|
|
2001-03-06 19:55:57 +01:00
|
|
|
|
|
|
|
<refsect1 id="app-pgrestore-examples">
|
2002-10-12 01:03:48 +02:00
|
|
|
<title>Examples</title>
|
2000-10-12 16:09:37 +02:00
|
|
|
|
2000-10-20 15:44:39 +02:00
|
|
|
<para>
|
2017-10-09 03:44:17 +02:00
|
|
|
Assume we have dumped a database called <literal>mydb</literal> into a
|
2006-11-26 19:11:11 +01:00
|
|
|
custom-format dump file:
|
2000-10-20 15:44:39 +02:00
|
|
|
|
2001-03-06 19:55:57 +01:00
|
|
|
<screen>
|
2006-11-26 19:11:11 +01:00
|
|
|
<prompt>$</prompt> <userinput>pg_dump -Fc mydb > db.dump</userinput>
|
2001-03-06 19:55:57 +01:00
|
|
|
</screen>
|
2000-10-20 15:44:39 +02:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2006-11-26 19:11:11 +01:00
|
|
|
To drop the database and recreate it from the dump:
|
2000-10-20 15:44:39 +02:00
|
|
|
|
2001-03-06 19:55:57 +01:00
|
|
|
<screen>
|
2006-11-26 19:11:11 +01:00
|
|
|
<prompt>$</prompt> <userinput>dropdb mydb</userinput>
|
|
|
|
<prompt>$</prompt> <userinput>pg_restore -C -d postgres db.dump</userinput>
|
2001-10-24 00:11:22 +02:00
|
|
|
</screen>
|
2006-11-26 19:11:11 +01:00
|
|
|
|
2017-10-09 03:44:17 +02:00
|
|
|
The database named in the <option>-d</option> switch can be any database existing
|
|
|
|
in the cluster; <application>pg_restore</application> only uses it to issue the
|
|
|
|
<command>CREATE DATABASE</command> command for <literal>mydb</literal>. With
|
|
|
|
<option>-C</option>, data is always restored into the database name that appears
|
2006-11-26 19:11:11 +01:00
|
|
|
in the dump file.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2017-10-09 03:44:17 +02:00
|
|
|
To reload the dump into a new database called <literal>newdb</literal>:
|
2006-11-26 19:11:11 +01:00
|
|
|
|
|
|
|
<screen>
|
|
|
|
<prompt>$</prompt> <userinput>createdb -T template0 newdb</userinput>
|
|
|
|
<prompt>$</prompt> <userinput>pg_restore -d newdb db.dump</userinput>
|
|
|
|
</screen>
|
|
|
|
|
2017-10-09 03:44:17 +02:00
|
|
|
Notice we don't use <option>-C</option>, and instead connect directly to the
|
2006-11-26 19:11:11 +01:00
|
|
|
database to be restored into. Also note that we clone the new database
|
2017-10-09 03:44:17 +02:00
|
|
|
from <literal>template0</literal> not <literal>template1</literal>, to ensure it is
|
2006-11-26 19:11:11 +01:00
|
|
|
initially empty.
|
2001-10-24 00:11:22 +02:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
To reorder database items, it is first necessary to dump the table of
|
|
|
|
contents of the archive:
|
|
|
|
<screen>
|
2006-11-26 19:11:11 +01:00
|
|
|
<prompt>$</prompt> <userinput>pg_restore -l db.dump > db.list</userinput>
|
2001-10-24 00:11:22 +02:00
|
|
|
</screen>
|
2007-02-01 01:28:19 +01:00
|
|
|
The listing file consists of a header and one line for each item, e.g.:
|
2001-10-24 00:11:22 +02:00
|
|
|
<programlisting>
|
|
|
|
;
|
2010-02-23 01:21:19 +01:00
|
|
|
; Archive created at Mon Sep 14 13:55:39 2009
|
|
|
|
; dbname: DBDEMOS
|
|
|
|
; TOC Entries: 81
|
|
|
|
; Compression: 9
|
|
|
|
; Dump Version: 1.10-0
|
2001-10-24 00:11:22 +02:00
|
|
|
; Format: CUSTOM
|
2010-02-23 01:21:19 +01:00
|
|
|
; Integer: 4 bytes
|
|
|
|
; Offset: 8 bytes
|
|
|
|
; Dumped from database version: 8.3.5
|
|
|
|
; Dumped by pg_dump version: 8.3.8
|
2001-10-24 00:11:22 +02:00
|
|
|
;
|
|
|
|
;
|
|
|
|
; Selected TOC Entries:
|
|
|
|
;
|
2010-02-23 01:21:19 +01:00
|
|
|
3; 2615 2200 SCHEMA - public pasha
|
|
|
|
1861; 0 0 COMMENT - SCHEMA public pasha
|
|
|
|
1862; 0 0 ACL - public pasha
|
|
|
|
317; 1247 17715 TYPE public composite pasha
|
|
|
|
319; 1247 25899 DOMAIN public domain0 pasha
|
2001-10-24 00:11:22 +02:00
|
|
|
</programlisting>
|
2003-03-24 15:32:51 +01:00
|
|
|
Semicolons start a comment, and the numbers at the start of lines refer to the
|
2001-10-24 00:11:22 +02:00
|
|
|
internal archive ID assigned to each item.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2007-02-01 01:28:19 +01:00
|
|
|
Lines in the file can be commented out, deleted, and reordered. For example:
|
2001-10-24 00:11:22 +02:00
|
|
|
<programlisting>
|
|
|
|
10; 145433 TABLE map_resolutions postgres
|
|
|
|
;2; 145344 TABLE species postgres
|
|
|
|
;4; 145359 TABLE nt_header postgres
|
|
|
|
6; 145402 TABLE species_records postgres
|
|
|
|
;8; 145416 TABLE ss_old postgres
|
|
|
|
</programlisting>
|
2003-03-24 15:32:51 +01:00
|
|
|
could be used as input to <application>pg_restore</application> and would only restore
|
|
|
|
items 10 and 6, in that order:
|
2001-10-24 00:11:22 +02:00
|
|
|
<screen>
|
2006-11-26 19:11:11 +01:00
|
|
|
<prompt>$</prompt> <userinput>pg_restore -L db.list db.dump</userinput>
|
2011-08-07 09:49:45 +02:00
|
|
|
</screen></para>
|
2000-10-20 15:44:39 +02:00
|
|
|
|
2001-03-06 19:55:57 +01:00
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
<title>See Also</title>
|
2000-10-20 15:44:39 +02:00
|
|
|
|
2001-03-06 19:55:57 +01:00
|
|
|
<simplelist type="inline">
|
|
|
|
<member><xref linkend="app-pgdump"></member>
|
|
|
|
<member><xref linkend="app-pg-dumpall"></member>
|
|
|
|
<member><xref linkend="app-psql"></member>
|
|
|
|
</simplelist>
|
2000-10-12 16:09:37 +02:00
|
|
|
</refsect1>
|
|
|
|
</refentry>
|