Re: Support tid range scan in parallel?
Cary Huang <cary.huang@highgo.ca>
From: Cary Huang <cary.huang@highgo.ca>
To: "David Rowley" <dgrowleyml@gmail.com>
Cc: "Pgsql Hackers" <pgsql-hackers@postgresql.org>
Date: 2024-05-09T17:16:32Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix possibly uninitialized HeapScanDesc.rs_startblock
- d167c19295da 19 (unreleased) landed
-
Add parallelism support for TID Range Scans
- 0ca3b16973a8 19 (unreleased) landed
-
Avoid repeating loads of frozen ID values.
- dd0183469bb7 17.0 cited
> I've not looked at the patch, but please add it to the July CF. I'll > try and look in more detail then. Thanks David, I have added this patch on July commitfest under the server feature category. I understand that the regression tests for parallel ctid range scan is a bit lacking now. It only has a few EXPLAIN clauses to ensure parallel workers are used when tid ranges are specified. They are added as part of select_parallel.sql test. I am not sure if it is more appropriate to have them as part of tidrangescan.sql test instead. So basically re-run the same test cases in tidrangescan.sql but in parallel? thank you Cary