Skip to content

Commit 7f1b5a6

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 cd259de commit 7f1b5a6

File tree

1 file changed

+8
-7
lines changed

1 file changed

+8
-7
lines changed

doc/src/sgml/config.sgml

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -4760,13 +4760,14 @@ ANY <replaceable class="parameter">num_sync</replaceable> ( <replaceable class="
47604760
<listitem>
47614761
<para>
47624762
Enables or disables the query planner's use of partitionwise grouping
4763-
or aggregation, which allows grouping or aggregation on a partitioned
4764-
tables performed separately for each partition. If the <literal>GROUP
4765-
BY</literal> clause does not include the partition keys, only partial
4766-
aggregation can be performed on a per-partition basis, and
4767-
finalization must be performed later. Because partitionwise grouping
4768-
or aggregation can use significantly more CPU time and memory during
4769-
planning, the default is <literal>off</literal>.
4763+
or aggregation, which allows grouping or aggregation on partitioned
4764+
tables to be performed separately for each partition. If the
4765+
<literal>GROUP BY</literal> clause does not include the partition
4766+
keys, only partial aggregation can be performed on a per-partition
4767+
basis, and finalization must be performed later. Because
4768+
partitionwise grouping or aggregation can use significantly more CPU
4769+
time and memory during planning, the default is
4770+
<literal>off</literal>.
47704771
</para>
47714772
</listitem>
47724773
</varlistentry>

0 commit comments

Comments
 (0)