summaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorPeter Eisentraut <peter_e@gmx.net>2018-06-04 15:03:15 -0400
committerPeter Eisentraut <peter_e@gmx.net>2018-06-04 15:03:15 -0400
commit4d6a854f176dbb48e62f017d8234f4736cb48d24 (patch)
tree2f2d8262c215287992fe97c19409a137eb0e8295 /doc/src
parent12b9affb32a636777062b3feb5816621363fc108 (diff)
Put new command-line options into alphabetical order
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/ref/pg_dump.sgml30
-rw-r--r--doc/src/sgml/ref/pg_dumpall.sgml30
2 files changed, 30 insertions, 30 deletions
diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml
index 50809b48443..64ced9fe045 100644
--- a/doc/src/sgml/ref/pg_dump.sgml
+++ b/doc/src/sgml/ref/pg_dump.sgml
@@ -805,6 +805,21 @@ PostgreSQL documentation
</varlistentry>
<varlistentry>
+ <term><option>--load-via-partition-root</option></term>
+ <listitem>
+ <para>
+ When dumping a <command>COPY</command> or <command>INSERT</command> statement for a partitioned table,
+ target the root of the partitioning hierarchy which contains it rather
+ than the partition itself. This may be useful when reloading data on
+ a server where rows do not always fall into the same partitions as
+ they did on the original server. This could happen, for example, if
+ the partitioning column is of type text and the two system have
+ different definitions of the collation used to partition the data.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
<term><option>--no-comments</option></term>
<listitem>
<para>
@@ -913,21 +928,6 @@ PostgreSQL documentation
</varlistentry>
<varlistentry>
- <term><option>--load-via-partition-root</option></term>
- <listitem>
- <para>
- When dumping a COPY or INSERT statement for a partitioned table,
- target the root of the partitioning hierarchy which contains it rather
- than the partition itself. This may be useful when reloading data on
- a server where rows do not always fall into the same partitions as
- they did on the original server. This could happen, for example, if
- the partitioning column is of type text and the two system have
- different definitions of the collation used to partition the data.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
<term><option>--section=<replaceable class="parameter">sectionname</replaceable></option></term>
<listitem>
<para>
diff --git a/doc/src/sgml/ref/pg_dumpall.sgml b/doc/src/sgml/ref/pg_dumpall.sgml
index 5d6fe9b87d5..8e5e7f9ef8a 100644
--- a/doc/src/sgml/ref/pg_dumpall.sgml
+++ b/doc/src/sgml/ref/pg_dumpall.sgml
@@ -343,6 +343,21 @@ PostgreSQL documentation
</varlistentry>
<varlistentry>
+ <term><option>--load-via-partition-root</option></term>
+ <listitem>
+ <para>
+ When dumping a <command>COPY</command> or <command>INSERT</command> statement for a partitioned table,
+ target the root of the partitioning hierarchy which contains it rather
+ than the partition itself. This may be useful when reloading data on
+ a server where rows do not always fall into the same partitions as
+ they did on the original server. This could happen, for example, if
+ the partitioning column is of type text and the two system have
+ different definitions of the collation used to partition the data.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
<term><option>--no-comments</option></term>
<listitem>
<para>
@@ -450,21 +465,6 @@ PostgreSQL documentation
</varlistentry>
<varlistentry>
- <term><option>--load-via-partition-root</option></term>
- <listitem>
- <para>
- When dumping a COPY or INSERT statement for a partitioned table,
- target the root of the partitioning hierarchy which contains it rather
- than the partition itself. This may be useful when reloading data on
- a server where rows do not always fall into the same partitions as
- they did on the original server. This could happen, for example, if
- the partitioning column is of type text and the two system have
- different definitions of the collation used to partition the data.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
<term><option>--use-set-session-authorization</option></term>
<listitem>
<para>