Bug #54965 | InnoDB: Warning: purge reached the head of the history list but it is still long | ||
---|---|---|---|
Submitted: | 2 Jul 2010 19:01 | Modified: | 9 Jul 2011 17:10 |
Reporter: | Mikhail Izioumtchenko | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: InnoDB Plugin storage engine | Severity: | S3 (Non-critical) |
Version: | 5.1, mysql-trunk-innodb | OS: | Any |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[2 Jul 2010 19:01]
Mikhail Izioumtchenko
[8 Jul 2010 15:48]
Omer Barnir
triage: setting tag to SRMRTBD (can be fixed but not required for GA as been there for a long time)
[12 Nov 2010 17:10]
Calvin Sun
likely a duplicate of bug#31123.
[7 Jan 2011 18:04]
Calvin Sun
Mark it as a duplicate of bug#31123.
[23 Jan 2011 14:03]
Matthew Lord
Could we re-triage this? Since this requires a full tablespace recreation, it seems like more than a D4. It's affected several customers too.
[9 Jul 2011 17:10]
Valeriy Kravchuk
The bug that this one was set as a duplicate of was closed, as bug reporter there found corruption of InnoDB files. Here this is not the case, as far as I understand, so I set this back to 'Verified".
[9 Jul 2011 17:13]
Valeriy Kravchuk
Bug #44923 was marked as a duplicate of this one.