Re: log sequence number InnoDB: is in the future!?

2013-02-01 Thread Larry Martell
On Mon, Jan 28, 2013 at 5:01 AM, walter harms wrote: > hi list, > > i am using mysql 5.1.53. > after a crash i have the follwing error in my log: > > 130128 10:45:25 InnoDB: Error: page 61 log sequence number 0 2871649158 > InnoDB: is in the future! Current system log sequence number 0 2494349480

Re: InnoDB interaction between secondary and primary keys.

2013-02-01 Thread Jeremy Chase
Thank you Rick! -- Jeremy Chase http://twitter.com/jeremychase On Wed, Jan 30, 2013 at 4:24 PM, Rick James wrote: > The hint of a change is in here (search for "secondary"): > > http://jorgenloland.blogspot.co.uk/2012/12/favorite-mysql-56-features-optimizer.html > > > -Original Message

RE: Can't drop table after crash

2013-02-01 Thread Rick James
Percona or SkySQL may be able to step in and repair it (for $$$). For the future, switching to XtraDB (as a plugin or as included in MariaDB) may give you more resilience to such crashes. > -Original Message- > From: Larry Martell [mailto:larry.mart...@gmail.com] > Sent: Friday, February