maria-developers team mailing list archive

Thread
Date

WL#247 New (by Igor): Make the optimizer use extended keys

To: maria-developers@xxxxxxxxxxxxxxxxxxx
From: worklog-noreply@xxxxxxxxxxxx
Date: Sat, 31 Dec 2011 05:49:35 +0000 (UTC)

-----------------------------------------------------------------------
                              WORKLOG TASK
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
TASK...........: Make the optimizer use extended keys
CREATION DATE..: Sat, 31 Dec 2011, 05:49
SUPERVISOR.....: 
IMPLEMENTOR....: Igor
COPIES TO......: Igor Monty Psergey Sanja Sergei Timour
CATEGORY.......: Server-BackLog
TASK ID........: 247 (http://askmonty.org/worklog/?tid=247)
VERSION........: Server-5.5
STATUS.........: Assigned
PRIORITY.......: 60
WORKED HOURS...: 0
ESTIMATE.......: 60 (hours remain)
ORIG. ESTIMATE.: 60

PROGRESS NOTES:



DESCRIPTION:

Currently the optimizer mostly does not use hidden components of InnoDB keys.
Meanwhile these components contain fields of the primary key and could be used
to to generate more efficient execution plans. In particular using these
components in many cases allow to generate execution plans that that employs
index only look-ups.

This task will support usage of extended keys for:
 - ref and eq-ref accesses
 - range scans
 - index-merge scans
 - loose scans 
 - min/max optimization 


ESTIMATED WORK TIME

ESTIMATED COMPLETION DATE
-----------------------------------------------------------------------
WorkLog (v4.0.0)