[PHOENIX-28] Optimizer not always correctly choosing point lookup plan

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.2.3
• Assignee: Unassigned
• Reporter: James R. Taylor
• Created: 07/Feb/14 23:45
• Updated: 21/Nov/15 02:16
• Resolved: 07/Feb/14 23:45

Description

Instead of always choosing a query plan that does a point lookup, the optimizer may choose one that instead prevents an ORDER BY, but causes a range scan instead. It's better (in the absence of stats) to choose the point lookup plan and do the ORDER BY on the results than to do a range scan with a filter on each row.