FB8-167: Add variable to force range plans if force index is used #967
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
percona-ysorokin
suggested changes
Feb 25, 2019
|
PR was updated according to comments. |
percona-ysorokin
approved these changes
Feb 26, 2019
Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Summary: Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Originally Reviewed By: hermanlee fbshipit-source-id: 4a4641b
|
Because of conflicts I removed changes in mysql-test/t/all_persisted_variables.test. This test has to be modified at let $total_persistent_vars=XXX; (+1 increase) and it should be re-recorded. |
inikep
changed the title
There was a problem hiding this comment.
@lth has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.
facebook-github-bot
pushed a commit
that referenced
this pull request
Mar 11, 2019
Summary: Because of conflicts I removed changes in mysql-test/t/all_persisted_variables.test. This test has to be modified at let $total_persistent_vars=XXX; (+1 increase) and it should be re-recorded. ``` Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Originally Reviewed By: hermanlee fbshipit-source-id: 4a4641b ``` Pull Request resolved: #967 Reviewed By: lth Differential Revision: D14387089 Pulled By: lth fbshipit-source-id: 49c95f15964
facebook-github-bot
pushed a commit
that referenced
this pull request
Mar 21, 2019
Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: #967 Reviewed By: lth Differential Revision: D14387089 Pulled By: lth fbshipit-source-id: 0525967
facebook-github-bot
pushed a commit
that referenced
this pull request
Nov 18, 2019
Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: #967 Reviewed By: lth Differential Revision: D14387089 Pulled By: lth fbshipit-source-id: 270826c
inikep
pushed a commit
to inikep/mysql-5.6
that referenced
this pull request
Jul 21, 2020
…cebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lth Differential Revision: D14387089 Pulled By: lth fbshipit-source-id: 270826c
inikep
pushed a commit
to inikep/mysql-5.6
that referenced
this pull request
Jul 23, 2020
…cebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lth Differential Revision: D14387089 Pulled By: lth fbshipit-source-id: 270826c
inikep
pushed a commit
to inikep/mysql-5.6
that referenced
this pull request
Jul 28, 2020
…cebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lth Differential Revision: D14387089 Pulled By: lth fbshipit-source-id: 270826c
inikep
pushed a commit
to inikep/mysql-5.6
that referenced
this pull request
Jun 23, 2023
…cebook#967) (facebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lloyd Differential Revision: D14387089 Pulled By: lth
hermanlee
pushed a commit
to hermanlee/mysql-5.6
that referenced
this pull request
Oct 3, 2023
…cebook#967) (facebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lloyd Differential Revision: D14387089 Pulled By: lth
hermanlee
pushed a commit
to hermanlee/mysql-5.6
that referenced
this pull request
Oct 18, 2023
…cebook#967) (facebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lloyd Differential Revision: D14387089 Pulled By: lth
inikep
pushed a commit
to inikep/percona-server
that referenced
this pull request
Apr 17, 2024
…rcona#967) (percona#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook/mysql-5.6@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook/mysql-5.6#967 Reviewed By: lloyd Differential Revision: D14387089 Pulled By: lth
inikep
pushed a commit
to inikep/mysql-5.6
that referenced
this pull request
Apr 23, 2024
…cebook#967) (facebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lloyd Differential Revision: D14387089 Pulled By: lth
inikep
pushed a commit
to inikep/mysql-5.6
that referenced
this pull request
Apr 23, 2024
…cebook#967) (facebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lloyd Differential Revision: D14387089 Pulled By: lth
inikep
pushed a commit
to inikep/mysql-5.6
that referenced
this pull request
Apr 25, 2024
…cebook#967) (facebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lloyd Differential Revision: D14387089 Pulled By: lth
inikep
pushed a commit
to inikep/mysql-5.6
that referenced
this pull request
May 7, 2024
…cebook#967) (facebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lloyd Differential Revision: D14387089 Pulled By: lth
inikep
pushed a commit
to inikep/mysql-5.6
that referenced
this pull request
May 8, 2024
…cebook#967) (facebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lloyd Differential Revision: D14387089 Pulled By: lth
inikep
pushed a commit
to inikep/mysql-5.6
that referenced
this pull request
May 9, 2024
…cebook#967) (facebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lloyd Differential Revision: D14387089 Pulled By: lth
inikep
pushed a commit
to inikep/mysql-5.6
that referenced
this pull request
May 10, 2024
…cebook#967) (facebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lloyd Differential Revision: D14387089 Pulled By: lth
inikep
pushed a commit
to inikep/mysql-5.6
that referenced
this pull request
May 13, 2024
…cebook#967) (facebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lloyd Differential Revision: D14387089 Pulled By: lth
inikep
pushed a commit
to inikep/mysql-5.6
that referenced
this pull request
May 15, 2024
…cebook#967) (facebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lloyd Differential Revision: D14387089 Pulled By: lth
inikep
pushed a commit
to inikep/mysql-5.6
that referenced
this pull request
May 16, 2024
…cebook#967) (facebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lloyd Differential Revision: D14387089 Pulled By: lth
inikep
pushed a commit
to inikep/mysql-5.6
that referenced
this pull request
May 17, 2024
…cebook#967) (facebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lloyd Differential Revision: D14387089 Pulled By: lth
inikep
pushed a commit
to inikep/mysql-5.6
that referenced
this pull request
May 17, 2024
…cebook#967) (facebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lloyd Differential Revision: D14387089 Pulled By: lth
inikep
pushed a commit
to inikep/mysql-5.6
that referenced
this pull request
May 21, 2024
…cebook#967) (facebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lloyd Differential Revision: D14387089 Pulled By: lth
inikep
pushed a commit
to inikep/mysql-5.6
that referenced
this pull request
May 21, 2024
…cebook#967) (facebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lloyd Differential Revision: D14387089 Pulled By: lth
inikep
pushed a commit
to inikep/mysql-5.6
that referenced
this pull request
May 30, 2024
…cebook#967) (facebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lloyd Differential Revision: D14387089 Pulled By: lth
inikep
pushed a commit
to inikep/mysql-5.6
that referenced
this pull request
Jun 14, 2024
…cebook#967) (facebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lloyd Differential Revision: D14387089 Pulled By: lth
inikep
pushed a commit
to inikep/mysql-5.6
that referenced
this pull request
Jun 19, 2024
…cebook#967) (facebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lloyd Differential Revision: D14387089 Pulled By: lth
inikep
pushed a commit
to inikep/mysql-5.6
that referenced
this pull request
Jun 20, 2024
…cebook#967) (facebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lloyd Differential Revision: D14387089 Pulled By: lth
inikep
pushed a commit
to inikep/mysql-5.6
that referenced
this pull request
Jun 21, 2024
…cebook#967) (facebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lloyd Differential Revision: D14387089 Pulled By: lth
inikep
pushed a commit
to inikep/mysql-5.6
that referenced
this pull request
Jun 25, 2024
…cebook#967) (facebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lloyd Differential Revision: D14387089 Pulled By: lth
inikep
pushed a commit
to inikep/mysql-5.6
that referenced
this pull request
Jul 2, 2024
…cebook#967) (facebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lloyd Differential Revision: D14387089 Pulled By: lth
inikep
pushed a commit
to inikep/mysql-5.6
that referenced
this pull request
Jul 19, 2024
…cebook#967) (facebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lloyd Differential Revision: D14387089 Pulled By: lth
inikep
pushed a commit
to inikep/mysql-5.6
that referenced
this pull request
Jul 19, 2024
…cebook#967) (facebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lloyd Differential Revision: D14387089 Pulled By: lth
inikep
pushed a commit
to inikep/mysql-5.6
that referenced
this pull request
Jul 31, 2024
…cebook#967) (facebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lloyd Differential Revision: D14387089 Pulled By: lth
inikep
pushed a commit
to inikep/mysql-5.6
that referenced
this pull request
Aug 2, 2024
…cebook#967) (facebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lloyd Differential Revision: D14387089 Pulled By: lth
inikep
pushed a commit
to inikep/mysql-5.6
that referenced
this pull request
Aug 6, 2024
…cebook#967) (facebook#967) Summary: Jira ticket: https://jira.percona.com/browse/FB8-167 Reference Patch: facebook@b01ff6a Currently, when force index is used, full table scans are highly penalized, but it is still possible to do a full index scan which is expensive. In many cases, we only use force index when we know there is better way to traverse the index, and not necessarily because we want a full index scan. To address these cases, add a session variable called optimizer_force_index_for_range, which when turned on, will try to search for a 'range' plan before falling back to an index plan. Pull Request resolved: facebook#967 Reviewed By: lloyd Differential Revision: D14387089 Pulled By: lth
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Because of conflicts I removed changes in mysql-test/t/all_persisted_variables.test. This test has to be modified at let $total_persistent_vars=XXX; (+1 increase) and it should be re-recorded.