database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-22 23:02:54 +03:00
Code

doc: Consistently use result set in documentation

Browse Source 
We use "result set" in all other places so let's be consistent
across the entire documentation.

Reported-by: grantgryczan@gmail.com
Discussion: https://postgr.es/m/172187924855.915373.15595156724215203822@wrigleys.postgresql.org
This commit is contained in:
Daniel Gustafsson 2024-09-02 18:36:57 +02:00
parent 2befd22790
commit 94eec79633
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/src/sgml/parallel.sgml
View File

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