From: Zhang Mingli <zmlpostgres@gmail.com>
To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Documentation refinement for Parallel Scans
Date: Thu, 20 Oct 2022 11:02:52 +0800
Message-ID: <17c99615-2c3b-4e4e-9d0b-424a66a7bccd@Spark> (raw)
In-Reply-To: <8b3760ce-5599-47d7-a4ca-06749e4d0b10@Spark>
References: <8b3760ce-5599-47d7-a4ca-06749e4d0b10@Spark>
Hi,
Found documents about parallel scan may be not so accurate.
As said in parallel.smgl:
```
In a parallel sequential scan, the table's blocks will be divided among the cooperating processes. Blocks are handed out one at a time, so that access to the table remains sequential.
```
To my understanding, this was right before. Because we return one block if a worker ask for before commit 56788d2156.
As comments inside table_block_parallelscan_nextpage:
```
Earlier versions of this would allocate the next highest block number to the next worker to call this function.
```
And from commit 56788d2156, each parallel worker will try to get ranges of blocks “chunks".
Access to the table remains sequential inside each worker’s process, but not across all workers or the parallel query.
Shall we update the documents?
Regards,
Zhang Mingli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: zmlpostgres@gmail.com, pgsql-hackers@lists.postgresql.org
Subject: Re: Documentation refinement for Parallel Scans
In-Reply-To: <17c99615-2c3b-4e4e-9d0b-424a66a7bccd@Spark>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox