aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeProjectSet.c
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2017-03-07 11:49:49 -0500
committerRobert Haas <rhaas@postgresql.org>2017-03-07 11:54:51 -0500
commit3bc7dafa9bebbdaa1bbf0da0798d29a8bdaf6a8f (patch)
tree0ce3dfc9ed46c7946ab58b42fc88e36b37adbedd /src/backend/executor/nodeProjectSet.c
parentef2662394455578f6c57e99a7896c69bdd9fbd74 (diff)
downloadpostgresql-3bc7dafa9bebbdaa1bbf0da0798d29a8bdaf6a8f.tar.gz
postgresql-3bc7dafa9bebbdaa1bbf0da0798d29a8bdaf6a8f.zip
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
Diffstat (limited to 'src/backend/executor/nodeProjectSet.c')
0 files changed, 0 insertions, 0 deletions