Force index in unique key range queries by timvaillancourt · Pull Request #1237 · github/gh-ost
Description
This PR forces the unique-key index to be used when gathering the min/max range of the unique key
This is to avoid possibilities of the optimizer picking a different index than we planned, discussed in more detail here. cc @morgo / @cyrinux
In case this PR introduced Go code changes:
- contributed code is using same conventions as original code
-
script/cibuildreturns with no formatting errors, build errors or unit test errors.