]> granicus.if.org Git - postgresql/commit
projects / postgresql / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: ef26623) | patch
Consider parallel merge joins.
authorRobert Haas <rhaas@postgresql.org>
Tue, 7 Mar 2017 16:49:49 +0000 (11:49 -0500)
committerRobert Haas <rhaas@postgresql.org>
Tue, 7 Mar 2017 16:54:51 +0000 (11:54 -0500)
commit3bc7dafa9bebbdaa1bbf0da0798d29a8bdaf6a8f
tree0ce3dfc9ed46c7946ab58b42fc88e36b37adbeddtree | snapshot
parentef2662394455578f6c57e99a7896c69bdd9fbd74commit | diff
Consider parallel merge joins.

Commit 45be99f8cd5d606086e0a458c9c72910ba8a613d took the position
that performing a merge join in parallel was not likely to work out
well, but this conclusion was greeted with skepticism even at the
time.  Whether it was true then or not, it's clearly not true any
more now that we have parallel index scan.

Dilip Kumar, reviewed by Amit Kapila and by me.

Discussion: http://postgr.es/m/CAFiTN-v3=cM6nyFwFGp0fmvY4=kk79Hq9Fgu0u8CSJ-EEq1Tiw@mail.gmail.com
src/backend/optimizer/path/joinpath.c diff | blob | history
src/test/regress/expected/select_parallel.out diff | blob | history
src/test/regress/sql/select_parallel.sql diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.