Skip to first unread message

Andrew Garner

Nov 11, 2010, 4:31:15 PM11/11/10
I brought this up a few days ago on percona-discuss, but perhaps
someone on percona-dev will have some insight.

Occasionally when upgrading from MySQL 5.0 to Percona-Server 5.1 in a
few different environments, I'm running into the
innodb_extra_undoslots assertion from trx/trx0undo.c. The original
datadir certainly wasn't using innodb-extra-undoslots before. Is
there any way to work around this without a mysqldump/restore?


Peter Zaitsev

Nov 11, 2010, 8:18:40 PM11/11/10

Would you mind to filing this as a bug. It is best if you have some repeatable test case (or may be you have small database you can upload)

I guess it is possible for MySQL 5.0 to initialize this space differently than MySQL 5.1 which makes Percona Server confused.

You received this message because you are subscribed to the Google Groups "Percona Dev" group.
To post to this group, send email to
To unsubscribe from this group, send email to
For more options, visit this group at

Peter Zaitsev, CEO, Percona Inc.
Tel: +1 888 401 3401 ext 501   Skype:  peter_zaitsev
24/7 Emergency Line +1 888 401 3401 ext 911

Percona Training Workshops
Reply all
Reply to author
0 new messages