mirror of
https://github.com/postgres/postgres.git
synced 2025-05-06 19:59:18 +03:00
Doc: fix grammatical errors for enable_partitionwise_aggregate
Author: Andrew Atkinson Reviewed-by: Ashutosh Bapat Discussion: https://postgr.es/m/CAG6XLEnC%3DEgq0YHRic2kWWDs4xwQnQ_kBA6qhhzAq1-pO_9Tfw%40mail.gmail.com Backpatch-through: 11, where enable_partitionwise_aggregate was added
This commit is contained in:
parent
916adc7c50
commit
245e0f4e8d
@ -5278,13 +5278,14 @@ ANY <replaceable class="parameter">num_sync</replaceable> ( <replaceable class="
|
||||
<listitem>
|
||||
<para>
|
||||
Enables or disables the query planner's use of partitionwise grouping
|
||||
or aggregation, which allows grouping or aggregation on a partitioned
|
||||
tables performed separately for each partition. If the <literal>GROUP
|
||||
BY</literal> clause does not include the partition keys, only partial
|
||||
aggregation can be performed on a per-partition basis, and
|
||||
finalization must be performed later. Because partitionwise grouping
|
||||
or aggregation can use significantly more CPU time and memory during
|
||||
planning, the default is <literal>off</literal>.
|
||||
or aggregation, which allows grouping or aggregation on partitioned
|
||||
tables to be performed separately for each partition. If the
|
||||
<literal>GROUP BY</literal> clause does not include the partition
|
||||
keys, only partial aggregation can be performed on a per-partition
|
||||
basis, and finalization must be performed later. Because
|
||||
partitionwise grouping or aggregation can use significantly more CPU
|
||||
time and memory during planning, the default is
|
||||
<literal>off</literal>.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
Loading…
x
Reference in New Issue
Block a user