Skip to content

Commit f114e16

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 6352f16 commit f114e16

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
@@ -5390,13 +5390,14 @@ ANY <replaceable class="parameter">num_sync</replaceable> ( <replaceable class="
53905390
<listitem>
53915391
<para>
53925392
Enables or disables the query planner's use of partitionwise grouping
5393-
or aggregation, which allows grouping or aggregation on a partitioned
5394-
tables performed separately for each partition. If the <literal>GROUP
5395-
BY</literal> clause does not include the partition keys, only partial
5396-
aggregation can be performed on a per-partition basis, and
5397-
finalization must be performed later. Because partitionwise grouping
5398-
or aggregation can use significantly more CPU time and memory during
5399-
planning, the default is <literal>off</literal>.
5393+
or aggregation, which allows grouping or aggregation on partitioned
5394+
tables to be performed separately for each partition. If the
5395+
<literal>GROUP BY</literal> clause does not include the partition
5396+
keys, only partial aggregation can be performed on a per-partition
5397+
basis, and finalization must be performed later. Because
5398+
partitionwise grouping or aggregation can use significantly more CPU
5399+
time and memory during planning, the default is
5400+
<literal>off</literal>.
54005401
</para>
54015402
</listitem>
54025403
</varlistentry>

0 commit comments

Comments
 (0)
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy