Commit952e0b2

committed

Doc: fix grammatical errors for enable_partitionwise_aggregate

Author: Andrew AtkinsonReviewed-by: Ashutosh BapatDiscussion:https://postgr.es/m/CAG6XLEnC%3DEgq0YHRic2kWWDs4xwQnQ_kBA6qhhzAq1-pO_9Tfw%40mail.gmail.comBackpatch-through: 11, where enable_partitionwise_aggregate was added

1 parentcd15bff commit952e0b2Copy full SHA for 952e0b2

File tree

-7

lines changed

-7

lines changed

Lines changed: 8 additions & 7 deletions

Original file line number	Diff line number	Diff line change
`@@ -5159,13 +5159,14 @@ ANY <replaceable class="parameter">num_sync</replaceable> ( <replaceable class="`
`5159`	`5159`	`<listitem>`
`5160`	`5160`	`<para>`
`5161`	`5161`	`Enables or disables the query planner's use of partitionwise grouping`
`5162`		`- or aggregation, which allows grouping or aggregation on a partitioned`
`5163`		`- tables performed separately for each partition. If the <literal>GROUP`
`5164`		`- BY</literal> clause does not include the partition keys, only partial`
`5165`		`- aggregation can be performed on a per-partition basis, and`
`5166`		`- finalization must be performed later. Because partitionwise grouping`
`5167`		`- or aggregation can use significantly more CPU time and memory during`
`5168`		`- planning, the default is <literal>off</literal>.`
	`5162`	`+ or aggregation, which allows grouping or aggregation on partitioned`
	`5163`	`+ tables to be performed separately for each partition. If the`
	`5164`	`+ <literal>GROUP BY</literal> clause does not include the partition`
	`5165`	`+ keys, only partial aggregation can be performed on a per-partition`
	`5166`	`+ basis, and finalization must be performed later. Because`
	`5167`	`+ partitionwise grouping or aggregation can use significantly more CPU`
	`5168`	`+ time and memory during planning, the default is`
	`5169`	`+ <literal>off</literal>.`
`5169`	`5170`	`</para>`
`5170`	`5171`	`</listitem>`
`5171`	`5172`	`</varlistentry>`

Comments

(0)