Commit7f1b5a6

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 parentcd259de commit7f1b5a6Copy full SHA for 7f1b5a6

File tree

-7

lines changed

-7

lines changed

Lines changed: 8 additions & 7 deletions

Original file line number	Diff line number	Diff line change
`@@ -4760,13 +4760,14 @@ ANY <replaceable class="parameter">num_sync</replaceable> ( <replaceable class="`
`4760`	`4760`	`<listitem>`
`4761`	`4761`	`<para>`
`4762`	`4762`	`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>.`
`4770`	`4771`	`</para>`
`4771`	`4772`	`</listitem>`
`4772`	`4773`	`</varlistentry>`

Comments

(0)