Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

LP #1674338: Extend index-only prefix index query optimisation to secondary indexes on generated columns

Description

**Reported in Launchpad by Laurynas Biveinis last update 20-03-2017 13:39:04

Percona Server 5.7 has ported Facebook prefix index query optimisation (https://github.com/percona/percona-server/pull/1505, https://github.com/percona/percona-server/pull/1506).

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.

Environment

None

Smart Checklist

Activity

Show:

Julia Vural March 4, 2025 at 9:21 PM

It appears that this issue is no longer being worked on, so we are closing it for housekeeping purposes. If you believe the issue still exists, please open a new ticket after confirming it's present in the latest release.

lpjirasync January 23, 2018 at 4:14 PM

**Comment from Launchpad by: Laurynas Biveinis on: 20-03-2017 13:39:04

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.

Won't Do

Details

Assignee

Reporter

Labels

Priority

Smart Checklist

Created January 23, 2018 at 4:14 PM
Updated March 4, 2025 at 9:21 PM
Resolved March 4, 2025 at 9:21 PM