Percona Server with XtraDB

fix innodb_max_purge_lag

Reported by Vadim Tkachenko on 2010-06-10
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server
Wishlist
Unassigned

Bug Description

http://dimitrik.free.fr/db_STRESS_MySQL_540_Purge_Lag_and_Ahead_Flushing_Fixed_Aug2009.html#note_5742

proposes to make
innodb_max_purge_lag working using next fix:

replace

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

to

         if (srv_max_purge_lag > 0 ) {

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
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers