@@ -804,6 +804,21 @@ PostgreSQL documentation
804804 </listitem>
805805 </varlistentry>
806806
807+ <varlistentry>
808+ <term><option>--load-via-partition-root</option></term>
809+ <listitem>
810+ <para>
811+ When dumping a <command>COPY</command> or <command>INSERT</command> statement for a partitioned table,
812+ target the root of the partitioning hierarchy which contains it rather
813+ than the partition itself. This may be useful when reloading data on
814+ a server where rows do not always fall into the same partitions as
815+ they did on the original server. This could happen, for example, if
816+ the partitioning column is of type text and the two system have
817+ different definitions of the collation used to partition the data.
818+ </para>
819+ </listitem>
820+ </varlistentry>
821+
807822 <varlistentry>
808823 <term><option>--no-comments</option></term>
809824 <listitem>
@@ -912,21 +927,6 @@ PostgreSQL documentation
912927 </listitem>
913928 </varlistentry>
914929
915- <varlistentry>
916- <term><option>--load-via-partition-root</option></term>
917- <listitem>
918- <para>
919- When dumping a COPY or INSERT statement for a partitioned table,
920- target the root of the partitioning hierarchy which contains it rather
921- than the partition itself. This may be useful when reloading data on
922- a server where rows do not always fall into the same partitions as
923- they did on the original server. This could happen, for example, if
924- the partitioning column is of type text and the two system have
925- different definitions of the collation used to partition the data.
926- </para>
927- </listitem>
928- </varlistentry>
929-
930930 <varlistentry>
931931 <term><option>--section=<replaceable class="parameter">sectionname</replaceable></option></term>
932932 <listitem>
0 commit comments