Remove grotty use of disable_cost for TID scan plans.
authorRobert Haas <rhaas@postgresql.org>
Mon, 22 Jul 2024 18:57:53 +0000 (14:57 -0400)
committerRobert Haas <rhaas@postgresql.org>
Mon, 22 Jul 2024 18:57:53 +0000 (14:57 -0400)
commite4326fbc60c44aab6df5849d3d67a0cba4c71cf2
treeaeb92879cd96545e37c5724c7ff8b91cfc2c72fc
parentc0348fd0e389c89003f309918705d1daea2217b0
Remove grotty use of disable_cost for TID scan plans.

Previously, the code charged disable_cost for CurrentOfExpr, and then
subtracted disable_cost from the cost of a TID path that used
CurrentOfExpr as the TID qual, effectively disabling all paths except
that one. Now, we instead suppress generation of the disabled paths
entirely, and generate only the one that the executor will actually
understand.

With this approach, we do not need to rely on disable_cost being
large enough to prevent the wrong path from being chosen, and we
save some CPU cycle by avoiding generating paths that we can't
actually use. In my opinion, the code is also easier to understand
like this.

Patch by me. Review by Heikki Linnakangas.

Discussion: http://postgr.es/m/591b3596-2ea0-4b8e-99c6-fad0ef2801f5@iki.fi
src/backend/optimizer/path/allpaths.c
src/backend/optimizer/path/costsize.c
src/backend/optimizer/path/tidpath.c
src/include/optimizer/paths.h