Re: Parallel Full Hash Join
Melanie Plageman <melanieplageman@gmail.com>
From: Melanie Plageman <melanieplageman@gmail.com>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2020-11-04T22:33:58Z
Lists: pgsql-hackers
Attachments
- v3-0001-Support-Parallel-FOJ-and-ROJ.patch (text/x-patch) patch v3-0001
I've attached a patch with the corrections I mentioned upthread. I've gone ahead and run pgindent, though, I can't say that I'm very happy with the result. I'm still not quite happy with the name BarrierArriveAndDetachExceptLast(). It's so literal. As you said, there probably isn't a nice name for this concept, since it is a function with the purpose of terminating parallelism. Regards, Melanie (Microsoft)
Commits
-
Remove overzealous assertion from PHJ.
- b37d051b0e59 16.0 landed
-
Remove comment obsoleted by 11c2d6fd.
- f303ec6210c4 16.0 landed
-
Parallel Hash Full Join.
- 11c2d6fdf5af 16.0 landed
-
Improve the naming of Parallel Hash Join phases.
- 8fba928fd788 16.0 landed
-
Update the names of Parallel Hash Join phases.
- 378802e3713c 14.0 landed
-
Add BarrierArriveAndDetachExceptLast().
- 7888b0999488 14.0 landed
-
Mop-up for wait event naming issues.
- 3048898e73c7 13.0 cited
-
Push tuple limits through Gather and Gather Merge.
- 3452dc5240da 11.0 cited