I've inherited a large MySQL 5.1 installation with 1000+ InnoDB tables in use across multiple databases.
I pulled out a list of all InnoDB tables from information_schema, and checked to see if those tables had an .ibd file.
Every single one has one. Yet every time there is an update to any of the InnoDB tables the shared ibdata1 still has it's mtime advanced?
Also, md5sums take of ibdata1 over the course of the day show that the values inside the file *are* changing (not the size obviously).
I'd really like to delete the ibdata1 file, but the fact that it is still being touched by MySQL makes me nervous.
Is there a way to proceed that doesn't involve me re-importing all my InnoDB tables "just to be sure"?
Some logical explanation why MySQL is touching the file perhaps?
Thanks for reading!
I pulled out a list of all InnoDB tables from information_schema, and checked to see if those tables had an .ibd file.
Every single one has one. Yet every time there is an update to any of the InnoDB tables the shared ibdata1 still has it's mtime advanced?
Also, md5sums take of ibdata1 over the course of the day show that the values inside the file *are* changing (not the size obviously).
I'd really like to delete the ibdata1 file, but the fact that it is still being touched by MySQL makes me nervous.
Is there a way to proceed that doesn't involve me re-importing all my InnoDB tables "just to be sure"?
Some logical explanation why MySQL is touching the file perhaps?
Thanks for reading!