-
Notifications
You must be signed in to change notification settings - Fork 4.1k
opt: extend hints to ZigZag joins #35814
Copy link
Copy link
Closed
Labels
A-sql-optimizerSQL logical planning and optimizations.SQL logical planning and optimizations.C-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)E-quick-winLikely to be a quick win for someone experienced.Likely to be a quick win for someone experienced.T-sql-queriesSQL Queries TeamSQL Queries Team
Description
We may want to offer some customers the ability to use zigzag joins for experimental purposes. If we do, we may want to force the selection of that join via hints. We can't currently do that:
root@localhost:26257/tpch> set experimental_enable_zigzag_join=true;
SET
Time: 593.804µs
root@localhost:26257/tpch> show experimental_enable_zigzag_join;
experimental_enable_zigzag_join
+---------------------------------+
on
(1 row)
Time: 1.00337ms
Then try with a hint:
root@localhost:26257/tpch> explain SELECT count(*) FROM lineitem INNER zigzag JOIN supplier ON l_suppkey = s_suppkey;
invalid syntax: statement ignored: syntax error at or near "zigzag"
DETAIL: source SQL:
explain SELECT count(*) FROM lineitem INNER zigzag JOIN supplier ON l_suppkey = s_suppkey
^
HINT: try \h <SOURCE>
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-sql-optimizerSQL logical planning and optimizations.SQL logical planning and optimizations.C-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)E-quick-winLikely to be a quick win for someone experienced.Likely to be a quick win for someone experienced.T-sql-queriesSQL Queries TeamSQL Queries Team
Type
Projects
Status
Done