From: | Zhang Mingli <zmlpostgres(at)gmail(dot)com> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Documentation refinement for Parallel Scans |
Date: | 2022-10-20 03:02:52 |
Message-ID: | 17c99615-2c3b-4e4e-9d0b-424a66a7bccd@Spark |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Dilip Kumar | 2022-10-20 03:18:46 | Re: Perform streaming logical transactions by background workers and parallel apply |
Previous Message | Kyotaro Horiguchi | 2022-10-20 02:59:46 | Re: Fix GetWALAvailability function code comments for WALAVAIL_REMOVED return value |