From 952e0b26c305126c8698af9f3fb3fa6d8ac07bf1 Mon Sep 17 00:00:00 2001
From: David Rowley <drowley@postgresql.org>
Date: Thu, 12 Oct 2023 21:16:43 +1300
Subject: [PATCH] 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
---
doc/src/sgml/config.sgml | 15 ++++++++-------
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 186f870fc75..0de813767f4 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -5159,13 +5159,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>
--
2.39.5