aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistbuild.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2015-08-12 21:18:45 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2015-08-12 21:19:04 -0400
commitec94bc1473475128ef4e7b62636e66effd314102 (patch)
tree9e3d55ae4c277ccc5e8c08beaeeb7a786880d903 /src/backend/access/gist/gistbuild.c
parentfc0a6402306db3cc93a5f760acabab687998be1d (diff)
downloadpostgresql-ec94bc1473475128ef4e7b62636e66effd314102.tar.gz
postgresql-ec94bc1473475128ef4e7b62636e66effd314102.zip
Undo mistaken tightening in join_is_legal().
One of the changes I made in commit 8703059c6b55c427 turns out not to have been such a good idea: we still need the exception in join_is_legal() that allows a join if both inputs already overlap the RHS of the special join we're checking. Otherwise we can miss valid plans, and might indeed fail to find a plan at all, as in recent report from Andreas Seltenreich. That code was added way back in commit c17117649b9ae23d, but I failed to include a regression test case then; my bad. Put it back with a better explanation, and a test this time. The logic does end up a bit different than before though: I now believe it's appropriate to make this check first, thereby allowing such a case whether or not we'd consider the previous SJ(s) to commute with this one. (Presumably, we already decided they did; but it was confusing to have this consideration in the middle of the code that was handling the other case.) Back-patch to all active branches, like the previous patch.
Diffstat (limited to 'src/backend/access/gist/gistbuild.c')
0 files changed, 0 insertions, 0 deletions