Merge lp:~laurynas-biveinis/percona-server/tokudb-prepare-scans into lp:percona-server/5.6
Status: | Merged |
---|---|
Approved by: | Alexey Kopytov |
Approved revision: | no longer in the source branch. |
Merged at revision: | 573 |
Proposed branch: | lp:~laurynas-biveinis/percona-server/tokudb-prepare-scans |
Merge into: | lp:percona-server/5.6 |
Diff against target: |
137 lines (+69/-2) 4 files modified
sql/handler.h (+38/-0) sql/opt_range.cc (+12/-0) sql/records.cc (+12/-2) sql/sql_executor.cc (+7/-0) |
To merge this branch: | bzr merge lp:~laurynas-biveinis/percona-server/tokudb-prepare-scans |
Related bugs: | |
Related blueprints: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Alexey Kopytov (community) | Approve | ||
Review via email: mp+212349@code.launchpad.net |
Description of the change
Handler extensions to notify SE of incoming index/range scan. Although ideally any required preparation actions should be added to existing methods (ha_index_init, read_range_first), or perhaps by exploiting ICP better, that's not trivial (e.g. cannot add TokuDB prelocking to ha_index_init if it is expensive, because ha_index_init is called to read few rows too). Investigating such changes is on Tokutek's TODO.
Add new handler methods for notifying storage engine of imminent index
scans, both for reading whole table and ranges. Implements
https:/
The new handler methods added, no-ops in default implementations:
- prepare_index_scan for imminent index (range-less) scan, called in
rr_index_first, rr_index_last in records.cc, and
join_read_
- prepare_range_scan for imminent index range scan, called in
QUICK_SELECT_
- prepare_
index (range-less) scan with used key part information, called in
join_read_
http://