ibdata1 and undo log

We are running MySQL 5.0.77, and implemented our first production InnoDB database a few months ago. The database is on a dedicated server and is composed of 14 tables. No tables have been added or dropped since creation. The ibdata1 file is growing much faster than the database itself. The

cope with deadlock

hi, From this url: http://dev.mysql.com/doc/refman/5.5/en/innodb-deadlocks.html , mysql says If you are using locking reads (|SELECT ... FOR UPDATE| http://dev.mysql.com/doc/refman/5.5/en/select.htmlor|SELECT ... LOCK IN SHARE MODE|), try using a lower isolation level such as|READ

Re: ibdata1 and undo log

- Original Message - From: Kay Rozeboom [DAS] kay.rozeb...@iowa.gov 1) Can anyone verify that the additional (presently unused) space was allocated for the undo log? 2) Are the many 1-page segments a leftover from a large undo log? I'm not too hot on the InnoDB