This worklog has been replaced with mariadb.org/jira

This site is here for historical purposes only. Do not add or edit tasks here!

 
 
 

WorkLog Frontpage Log in / Register
High-Level Description | Task Dependencies | High-Level Specification | Low-Level Design | File Attachments | User Comments | Time Estimates | Funding and Votes | Progress Reports

 Make the optimizer use extended keys
Title
Task ID247
Queue
Version
Status
Priority
Copies toIgor
Monty
Psergey
Sanja
Sergei
Timour

Created byIgor31 Dec 2011Done
Supervisor   
Lead Architect    
Architecture Review  
Implementor  
Code Review  
QA  
Documentation  
 High-Level 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 allows to generate execution plans that employ
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 
 Task Dependencies
Others waiting for Task 247Task 247 is waiting forGraph
 
 High-Level Specification
 Low-Level Design
 File Attachments
 NameTypeSizeByDate
 User Comments
 Time Estimates
NameHours WorkedLast Updated
Total0 
 Hrs WorkedProgressCurrentOriginal
This Task06060
Total06060
 
 Funding and Votes
Votes: 0: 0%
 Make vote: Useless    Nice to have    Important    Very important    

Funding: 0 offers, total 0 Euro
 Progress Reports
(Igor - Sat, 31 Dec 2011, 20:54
    
High Level Description modified.
--- /tmp/wklog.247.old.453	2011-12-31 20:54:38.000000000 +0000
+++ /tmp/wklog.247.new.453	2011-12-31 20:54:38.000000000 +0000
@@ -1,7 +1,7 @@
 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 allows to generate execution plans that employs
+components in many cases allows to generate execution plans that employ
 index only look-ups.
 
 This task will support usage of extended keys for:

(Igor - Sat, 31 Dec 2011, 20:53
    
High Level Description modified.
--- /tmp/wklog.247.old.434	2011-12-31 20:53:54.000000000 +0000
+++ /tmp/wklog.247.new.434	2011-12-31 20:53:54.000000000 +0000
@@ -1,7 +1,7 @@
 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
+components in many cases allows to generate execution plans that employs
 index only look-ups.
 
 This task will support usage of extended keys for:

(Igor - Sat, 31 Dec 2011, 20:52
    
Category updated.
--- /tmp/wklog.247.old.32649	2011-12-31 20:52:48.000000000 +0000
+++ /tmp/wklog.247.new.32649	2011-12-31 20:52:48.000000000 +0000
@@ -1,2 +1,2 @@
-Server-BackLog
+Server-Sprint
 

(Igor - Sat, 31 Dec 2011, 20:52
    
Supervisor updated:  -> Igor


Report Generator:
 
Saved Reports:

WorkLog v4.0.0
  © 2010  Sergei Golubchik and Monty Program AB
  © 2004  Andrew Sweger <yDNA@perlocity.org> and Addnorya
  © 2003  Matt Wagner <matt@mysql.com> and MySQL AB