MySQL Bugs: #62759: in mysql.err log , InnoDB: Warning: purge reached the head of the history list,

Bug #62759	in mysql.err log , InnoDB: Warning: purge reached the head of the history list,
Submitted:	16 Oct 2011 13:46	Modified:	22 Dec 2011 20:03
Reporter:	ws lee	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S3 (Non-critical)
Version:	5.0.51a	OS:	Solaris (5.10)
Assigned to:		CPU Architecture:	Any

Description:
in mysql.err, next error message producing about 10 secounds inerval.

111016 22:39:24  InnoDB: Warning: purge reached the head of the history list,
InnoDB: but its length is still reported as 32686! Make a detailed bug
InnoDB: report, and post it to bugs.mysql.com
111016 22:39:34  InnoDB: Warning: purge reached the head of the history list,
InnoDB: but its length is still reported as 32687! Make a detailed bug
InnoDB: report, and post it to bugs.mysql.com
111016 22:39:44  InnoDB: Warning: purge reached the head of the history list,
InnoDB: but its length is still reported as 32688! Make a detailed bug
InnoDB: report, and post it to bugs.mysql.com
111016 22:39:54  InnoDB: Warning: purge reached the head of the history list,
InnoDB: but its length is still reported as 32689! Make a detailed bug
InnoDB: report, and post it to bugs.mysql.com
111016 22:40:04  InnoDB: Warning: purge reached the head of the history list,
InnoDB: but its length is still reported as 32691! Make a detailed bug
InnoDB: report, and post it to bugs.mysql.com
111016 22:40:14  InnoDB: Warning: purge reached the head of the history list,
InnoDB: but its length is still reported as 32693! Make a detailed bug
InnoDB: report, and post it to bugs.mysql.com
111016 22:40:24  InnoDB: Warning: purge reached the head of the history list,
InnoDB: but its length is still reported as 32701! Make a detailed bug
InnoDB: report, and post it to bugs.mysql.com
111016 22:40:34  InnoDB: Warning: purge reached the head of the history list,
InnoDB: but its length is still reported as 32703! Make a detailed bug
InnoDB: report, and post it to bugs.mysql.com
111016 22:40:47  InnoDB: Warning: purge reached the head of the history list,
InnoDB: but its length is still reported as 32716! Make a detailed bug
InnoDB: report, and post it to bugs.mysql.com
111016 22:40:57  InnoDB: Warning: purge reached the head of the history list,
InnoDB: but its length is still reported as 32719! Make a detailed bug
InnoDB: report, and post it to bugs.mysql.com
111016 22:41:17  InnoDB: Warning: purge reached the head of the history list,
InnoDB: but its length is still reported as 32720! Make a detailed bug
InnoDB: report, and post it to bugs.mysql.com
111016 22:41:28  InnoDB: Warning: purge reached the head of the history list,
InnoDB: but its length is still reported as 32721! Make a detailed bug
InnoDB: report, and post it to bugs.mysql.com
111016 22:41:38  InnoDB: Warning: purge reached the head of the history list,
InnoDB: but its length is still reported as 32724! Make a detailed bug
InnoDB: report, and post it to bugs.mysql.com

How to repeat:
in mysql.err , repeatedly error message producing.

Suggested fix:
can fix this bug mysqlcheck?

To. MySQL person of charge

if i dont' t fix this problem, occur any big problem?
please reply.

Please, check if this problem ever happens with a newer version, 5.0.91+. 

As for how "safe" this situation is, I do not expect any problems if server continues to work. Problems are possible in case of crash immediately after this warning, IMHO.

thanks for reply.
I can't restart current mysql server.
so, I can't check new version.
In this situation, if big problem not occur i only observe this problem.

Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.mysql.com/how-to-report.php

If you can provide more information, feel free to add it to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.

As you can not upgrade and provide us information how it behaves in new version, so I close the bug. Feel free to re-open it if you meet it again in any current version (5.0.91, 5.1.60 or 5.5.19 at time when this comment is written).

Related Bug #82213