Hello Geetanjali,
On 8/26/2014 1:16 AM, geetanjali mehra wrote:
I want to understand how to tune innodb_max_purge_lag
<http://dev.mysql.com/doc/refman/5.5/en/innodb-parameters.html#sysvar_innodb_max_purge_lag>
when history list length is high.
Could anyone explain me.
Best Regards,
Geetanjali Mehra
Senior Oracle and MySQL DBA Corporate Trainer and Database Security
Specialist
This setting not related to the history value. It is there to help
control the gap between these two values of the InnoDB status report
Trx id counter 0 290328385
Purge done for trx's n:o < 0 290315608 undo n:o < 0 17
What is the current transaction compared what is the oldest transaction
that still has aged copies of data left in the data area of the
tablespace. The difference between those two values is the "purge backlog"
Yours,
--
Shawn Green
MySQL Senior Principal Technical Support Engineer
Oracle USA, Inc. - Hardware and Software, Engineered to Work Together.
Office: Blountville, TN
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql
