planner: regard NULL as point when accessing composite index #29992
Conversation
|
[REVIEW NOTIFICATION] This pull request has not been approved. To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
ti-chi-bot
added
release-note
|
@qw4990: PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
| @@ -1857,6 +1857,10 @@ var defaultSysVars = []*SysVar{ | |||
| s.EnablePseudoForOutdatedStats = TiDBOptOn(val) | |||
| return nil | |||
| }}, | |||
| {Scope: ScopeGlobal | ScopeSession, Name: TiDBRegardNULLAsPoint, Value: BoolToOnOff(DefTiDBRegardNULLAsPoint), Type: TypeBool, SetSession: func(s *SessionVars, val string) error { | |||
| s.StmtCtx.RegardNULLAsPoint = TiDBOptOn(val) | |||
There was a problem hiding this comment.
According to ResetContextOfStmt(), which will be called in ExecuteStmt(), there will be a new StmtCtx every time when you execute a statement.
Line 1855 in 78c653e
Seems we should put the option in
SessionVars.
|
Close since it's duplicated with #30244 |
What problem does this PR solve?
Issue Number: close #29650
Problem Summary: planner: regard NULL as point when accessing composite index
What is changed and how it works?
planner: regard NULL as point when accessing composite index
Check List
Tests
Release note