Extend index-only prefix index query optimisation to secondary indexes on generated columns
Bug #1674338 reported by
Laurynas Biveinis
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.5 |
Invalid
|
Undecided
|
Unassigned | |||
5.6 |
Invalid
|
Undecided
|
Unassigned | |||
5.7 |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
Percona Server 5.7 has ported Facebook prefix index query optimisation (https:/
Extend this optimisation to apply to secondary indexes on generated columns too. A superficial review seems to show that this might be involved, as server always requests base column image from the storage engine on the queries that this optimisation might apply.
To post a comment you must log in.
Relevant 5.7 worklogs:
WL#8149 B-tree Index Support on non-materialized virtual columns
WL#8114 Don't store virtual generated columns in database
WL#8227 Support SEs to create index on virtual generated columns
WL#8481 Callback for computation of virtual column index values
from InnoDB purge threads
All 4 worklogs are to support virtual column and virtual index on such
columns.