Alex,
this mysql/innobase/trx/trx0undo.c prints trace information
on what it finds at database startup.
Could you try compiling a new mysqld and try starting the database
with the new mysqld. Obviously the recovery goes into an infinite loop,
and this helps to find out why.
Regards,
Heikki
-
Bonjour Heikki,
In fact this morning Mysql is ... crashed on this server :(
It never crashed with 3.23.38 :(
I don't yet know if this is really a 3.23.39 problem or something
else.
If I'm able to restart Mysql, I will downgrade to 3.23.38 in order
to see if it's back to th
;
Cc: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Monday, June 18, 2001 6:24 PM
Subject: 3.23.39+InnoDB = slower than 3.23.389InnoDB ?
>Bonjour,
>
> Environment: Solaris 2.8 on SPARC 64bit, Mysql-3.23.39+InnoDB.
>
> Mysql 3.23.38 with InnoDB support have been running for a wh
Bonjour,
Environment: Solaris 2.8 on SPARC 64bit, Mysql-3.23.39+InnoDB.
Mysql 3.23.38 with InnoDB support have been running for a while now
on one of my servers (for a month in fact, since the release of
3.23.38).
It worked perfectly well and was able to handle the job (intens
