mirror of
https://github.com/postgres/postgres.git
synced 2025-07-02 09:02:37 +03:00
Massive overhaul of pg_dump: make use of dependency information from
pg_depend to determine a safe dump order. Defaults and check constraints can be emitted either as part of a table or domain definition, or separately if that's needed to break a dependency loop. Lots of old half-baked code for controlling dump order removed.
This commit is contained in:
@ -1,4 +1,4 @@
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_restore.sgml,v 1.44 2003/11/29 19:51:39 pgsql Exp $ -->
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_restore.sgml,v 1.45 2003/12/06 03:00:10 tgl Exp $ -->
|
||||
|
||||
<refentry id="APP-PGRESTORE">
|
||||
<refmeta>
|
||||
@ -227,35 +227,6 @@
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><option>-N</option></term>
|
||||
<term><option>--orig-order</option></term>
|
||||
<listitem>
|
||||
<para>
|
||||
Restore items in the order they were originally generated within
|
||||
<application>pg_dump</application>. This option has no known
|
||||
practical use, since <application>pg_dump</application> generates
|
||||
the items in an order convenient to it, which is unlikely to be a
|
||||
safe order for restoring them. (This is <emphasis>not</> the order
|
||||
in which the items are ultimately listed in the archive's table of
|
||||
contents.) See also <option>-r</>.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><option>-o</option></term>
|
||||
<term><option>--oid-order</option></term>
|
||||
<listitem>
|
||||
<para>
|
||||
Restore items in order by OID. This option is of limited usefulness,
|
||||
since OID is only an approximate indication of original creation
|
||||
order. This option overrides <option>-N</> if both are specified.
|
||||
See also <option>-r</>.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><option>-O</option></term>
|
||||
<term><option>--no-owner</option></term>
|
||||
@ -287,31 +258,6 @@
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><option>-r</option></term>
|
||||
<term><option>--rearrange</option></term>
|
||||
<listitem>
|
||||
<para>
|
||||
Rearrange items by object type (this occurs after the sorting
|
||||
specified by <option>-N</option> or <option>-o</option>, if
|
||||
given). The rearrangement is intended to give the best possible
|
||||
restore performance.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
When none of <option>-N</option>, <option>-o</option>, and
|
||||
<option>-r</> appear, <application>pg_restore</application> restores
|
||||
items in the order they appear in the dump's table of contents,
|
||||
or in the order they appear in the <REPLACEABLE
|
||||
CLASS="PARAMETER">list-file</REPLACEABLE> if <option>-L</> is
|
||||
given. The combination of <option>-o</> and <option>-r</>
|
||||
duplicates the sorting done by <application>pg_dump</application>
|
||||
before creating the dump's table of contents,
|
||||
and so it is normally unnecessary to specify it.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><option>-R</option></term>
|
||||
<term><option>--no-reconnect</option></term>
|
||||
|
Reference in New Issue
Block a user