Refactor innodb_adaptive_checkpoint

Bug #689450 reported by Vadim Tkachenko on 2010-12-12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to
Fix Released

Bug Description

In Percona 5.5 I propose to remove

We should reuse
innodb_adaptive_flushing variable.

In MySQL 5.5 it is boolean variable, but we can make it accepting several parameters:
0 or OFF |
native ( use InnoDB-plugin adaptive_flushing) |
estimate |

Do we need to keep reflex ?

Changed in percona-server:
assignee: nobody → Yasufumi Kinoshita (yasufumi-kinoshita)
milestone: none → 5.5-20beta
Changed in percona-server:
importance: Undecided → Medium
status: New → Confirmed

I don't accept.
The exist parameter "innodb_adaptive_flushing" should not be changed.

innnodb_adaptive_flushing_method = [native | estimate | keep_average ]
is acceptable. I will implement.

Changed in percona-server:
status: Confirmed → In Progress
Changed in percona-server:
status: In Progress → Fix Committed
Changed in percona-server:
status: Fix Committed → Fix Released

Percona now uses JIRA for bug reports so this bug report is migrated to:

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers