Skip to content
This repository has been archived by the owner on Jul 26, 2022. It is now read-only.

Fix upstream optimizer bug on OR condition (Bug #75248) #38

Closed
yoshinorim opened this issue Feb 25, 2015 · 0 comments
Closed

Fix upstream optimizer bug on OR condition (Bug #75248) #38

yoshinorim opened this issue Feb 25, 2015 · 0 comments
Assignees
@yoshinorim

Comments

@yoshinorim
Copy link

http://bugs.mysql.com/bug.php?id=75248 affects more in RocksDB than InnoDB because of costly range scan. MariaDB already fixed the problem and we already identified one line diff to fix the problem. We need to decide 1. waiting until Oracle fixes the bug and cloning into WebScaleSQL or 2. fixing WebScaleSQL directly
@yoshinorim yoshinorim self-assigned this Feb 25, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@yoshinorim yoshinorim

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@yoshinorim