Commitf114e16

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 parent6352f16 commitf114e16Copy full SHA for f114e16

File tree

-7

lines changed

-7

lines changed

Lines changed: 8 additions & 7 deletions

Original file line number	Diff line number	Diff line change
`@@ -5390,13 +5390,14 @@ ANY <replaceable class="parameter">num_sync</replaceable> ( <replaceable class="`
`5390`	`5390`	`<listitem>`
`5391`	`5391`	`<para>`
`5392`	`5392`	`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>.`
`5400`	`5401`	`</para>`
`5401`	`5402`	`</listitem>`
`5402`	`5403`	`</varlistentry>`

Comments

(0)