Remove optimizer_fix
Bug #986247 reported by
Alexey Kopytov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
Low
|
Stewart Smith | ||
| 5.1 |
Won't Fix
|
Low
|
Unassigned | ||
| 5.5 |
Fix Released
|
Low
|
Stewart Smith | ||
Bug Description
We should document optimizer_fix.patch and the optimizer_fix variable it introduces.
Related branches
lp:~stewart/percona-server/bug986247-remove-optimizer-fix
- Laurynas Biveinis (community): Needs Fixing
- George Ormond Lorch III (community): Approve (g2)
-
Diff: 130 lines (+6/-36)4 files modifiedPercona-Server/patch_info/optimizer_fix.info (+0/-8)
Percona-Server/sql/mysqld.cc (+2/-1)
Percona-Server/sql/opt_range.cc (+4/-22)
Percona-Server/sql/sql_select.cc (+0/-5)
lp:~stewart/percona-server/5.5-bug986247-remove-optimizer-fix
- Laurynas Biveinis (community): Approve
- George Ormond Lorch III (community): Approve (g2)
-
Diff: 146 lines (+8/-38)5 files modifiedPercona-Server/mysql-test/r/select.result (+2/-2)
Percona-Server/patch_info/optimizer_fix.info (+0/-8)
Percona-Server/sql/opt_range.cc (+4/-22)
Percona-Server/sql/sql_select.cc (+0/-5)
Percona-Server/sql/sys_vars.cc (+2/-1)
| tags: | added: doc |
| Changed in percona-server: | |
| status: | New → Confirmed |
| Changed in percona-server: | |
| assignee: | nobody → Hrvoje Matijakovic (hrvojem) |
| Changed in percona-server: | |
| importance: | Undecided → Low |
| status: | Confirmed → Triaged |
| Changed in percona-server: | |
| status: | Triaged → In Progress |
Revision history for this message
| Alexey Kopytov (akopytov) wrote | #1 |
| summary: |
- Document optimizer_fix + Remove optimizer_fix |
| tags: | removed: doc |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #2 |
To post a comment you must log in.
As no one seems to know what were the reasons to implement optimizer_fix, let's convert this bug to a request to remove optimizer_fix. I think it should be safe to actually remove it, rather than go through a deprecation procedure.