]> granicus.if.org Git - postgresql/commit
Further mucking with PlaceHolderVar-related restrictions on join order.
authorTom Lane <tgl@sss.pgh.pa.us>
Mon, 10 Aug 2015 21:18:17 +0000 (17:18 -0400)
committerTom Lane <tgl@sss.pgh.pa.us>
Mon, 10 Aug 2015 21:18:17 +0000 (17:18 -0400)
commitfda25b22018095fa86bee5a31920344976eb7479
tree315e5fa78bd59398d281fc1d2e6574e7ed5c7a6f
parent0ae43b6a631ce8507ef4bd68ce297853a8986fe8
Further mucking with PlaceHolderVar-related restrictions on join order.

Commit 85e5e222b1dd02f135a8c3bf387d0d6d88e669bd turns out not to have taken
care of all cases of the partially-evaluatable-PlaceHolderVar problem found
by Andreas Seltenreich's fuzz testing.  I had set it up to check for risky
PHVs only in the event that we were making a star-schema-based exception to
the param_source_rels join ordering heuristic.  However, it turns out that
the problem can occur even in joins that satisfy the param_source_rels
heuristic, in which case allow_star_schema_join() isn't consulted.
Refactor so that we check for risky PHVs whenever the proposed join has
any remaining parameterization.

Back-patch to 9.2, like the previous patch (except for the regression test
case, which only works back to 9.3 because it uses LATERAL).

Note that this discovery implies that problems of this sort could've
occurred in 9.2 and up even before the star-schema patch; though I've not
tried to prove that experimentally.
src/backend/optimizer/path/joinpath.c
src/test/regress/expected/join.out
src/test/regress/sql/join.sql