innodb_extra_undoslots

19 views
Skip to first unread message

Andrew Garner

unread,
Nov 11, 2010, 4:31:15 PM11/11/10
to perco...@googlegroups.com
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?

~Andrew

Peter Zaitsev

unread,
Nov 11, 2010, 8:18:40 PM11/11/10
to perco...@googlegroups.com
Andrew,

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)
https://bugs.launchpad.net/percona-server/+filebug

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 perco...@googlegroups.com.
To unsubscribe from this group, send email to percona-dev...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/percona-dev?hl=en.




--
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
http://www.percona.com/training/
Reply all
Reply to author
Forward
0 new messages