fix innodb_max_purge_lag

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

Bug Description

proposes to make
innodb_max_purge_lag working using next fix:


         if (srv_max_purge_lag > 0
              && !UT_LIST_GET_LAST(trx_sys->view_list)) {


         if (srv_max_purge_lag > 0 ) {

Related branches

Changed in percona-server:
status: New → Triaged
importance: Undecided → Wishlist
assignee: nobody → Yasufumi Kinoshita (yasufumi-kinoshita)
milestone: none → 5.1-12.0
Changed in percona-server:
milestone: 5.1.47-12.0 → 5.1-12.0
Changed in percona-server:
status: Triaged → 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