Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit dab5538

Browse files
committed
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
1 parent f0c409d commit dab5538

File tree

1 file changed

+8
-7
lines changed

1 file changed

+8
-7
lines changed

doc/src/sgml/config.sgml

+8-7
Original file line numberDiff line numberDiff line change
@@ -5271,13 +5271,14 @@ ANY <replaceable class="parameter">num_sync</replaceable> ( <replaceable class="
52715271
<listitem>
52725272
<para>
52735273
Enables or disables the query planner's use of partitionwise grouping
5274-
or aggregation, which allows grouping or aggregation on a partitioned
5275-
tables performed separately for each partition. If the <literal>GROUP
5276-
BY</literal> clause does not include the partition keys, only partial
5277-
aggregation can be performed on a per-partition basis, and
5278-
finalization must be performed later. Because partitionwise grouping
5279-
or aggregation can use significantly more CPU time and memory during
5280-
planning, the default is <literal>off</literal>.
5274+
or aggregation, which allows grouping or aggregation on partitioned
5275+
tables to be performed separately for each partition. If the
5276+
<literal>GROUP BY</literal> clause does not include the partition
5277+
keys, only partial aggregation can be performed on a per-partition
5278+
basis, and finalization must be performed later. Because
5279+
partitionwise grouping or aggregation can use significantly more CPU
5280+
time and memory during planning, the default is
5281+
<literal>off</literal>.
52815282
</para>
52825283
</listitem>
52835284
</varlistentry>

0 commit comments

Comments
 (0)