1
0
mirror of https://github.com/postgres/postgres.git synced 2025-07-03 20:02:46 +03:00

Rename enable_incrementalsort for clarity

Author: James Coleman <jtc331@gmail.com>
Discussion: https://www.postgresql.org/message-id/flat/df652910-e985-9547-152c-9d4357dc3979%402ndquadrant.com
This commit is contained in:
Peter Eisentraut
2020-07-05 11:41:52 +02:00
parent c536da177c
commit 94e454cddf
13 changed files with 25 additions and 25 deletions

View File

@ -4574,10 +4574,10 @@ ANY <replaceable class="parameter">num_sync</replaceable> ( <replaceable class="
</listitem>
</varlistentry>
<varlistentry id="guc-enable-incrementalsort" xreflabel="enable_incrementalsort">
<term><varname>enable_incrementalsort</varname> (<type>boolean</type>)
<varlistentry id="guc-enable-incremental-sort" xreflabel="enable_incremental_sort">
<term><varname>enable_incremental_sort</varname> (<type>boolean</type>)
<indexterm>
<primary><varname>enable_incrementalsort</varname> configuration parameter</primary>
<primary><varname>enable_incremental_sort</varname> configuration parameter</primary>
</indexterm>
</term>
<listitem>

View File

@ -588,7 +588,7 @@ Author: Tomas Vondra <tomas.vondra@postgresql.org>
-->
<para>
Implement <link linkend="guc-enable-incrementalsort">incremental
Implement <link linkend="guc-enable-incremental-sort">incremental
sorting</link> (James Coleman, Alexander Korotkov, Tomas Vondra)
</para>
@ -596,7 +596,7 @@ Author: Tomas Vondra <tomas.vondra@postgresql.org>
If a result is already sorted by several leading keys, this
allows for batch sorting of additional trailing keys because the
previous keys are already equal. This is controlled by <xref
linkend="guc-enable-incrementalsort"/>.
linkend="guc-enable-incremental-sort"/>.
</para>
</listitem>