Commit94eec79

committed

doc: Consistently use result set in documentation

We use "result set" in all other places so let's be consistentacross the entire documentation.Reported-by: grantgryczan@gmail.comDiscussion:https://postgr.es/m/172187924855.915373.15595156724215203822@wrigleys.postgresql.org

1 parent2befd22 commit94eec79Copy full SHA for 94eec79

File tree

-1

lines changed

-1

lines changed

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -423,7 +423,7 @@ EXPLAIN SELECT * FROM pgbench_accounts WHERE filler LIKE '%x%';`
`423`	`423`	`Append</literal> node can have both partial and non-partial child plans.`
`424`	`424`	`Non-partial children will be scanned by only a single process, since`
`425`	`425`	`scanning them more than once would produce duplicate results. Plans that`
`426`		`- involve appending multipleresults sets can therefore achieve`
	`426`	`+ involve appending multipleresult sets can therefore achieve`
`427`	`427`	`coarse-grained parallelism even when efficient partial plans are not`
`428`	`428`	`available. For example, consider a query against a partitioned table`
`429`	`429`	`that can only be implemented efficiently by using an index that does`

Comments

(0)