Our incremental backups seem to be filling with instances of ib_logfile1,
ib_logfile2, and ibdata1.
I know that changing a single byte in a single INNODB table causes these files
to be touched.
I put innodb_file_per_table in /etc/my.cnf, but apparently, that only causes
new databases to be
Dump the entire DB, drop the DB, restore the DB.
On Fri, Feb 11, 2011 at 11:53 AM, Jan Steinman j...@bytesmiths.com wrote:
Our incremental backups seem to be filling with instances of ib_logfile1,
ib_logfile2, and ibdata1.
I know that changing a single byte in a single INNODB table causes
, 2011 12:53 PM
To: mysql@lists.mysql.com
Subject: Converting INNODB to file-per-table?
Our incremental backups seem to be filling with instances of ib_logfile1,
ib_logfile2, and ibdata1.
I know that changing a single byte in a single INNODB table causes these files
to be touched.
I put
)
AIM Skype : RolandoLogicWorx
redwa...@logicworks.net
http://www.linkedin.com/in/rolandoedwards
-Original Message-
From: Jan Steinman [mailto:j...@bytesmiths.com]
Sent: Friday, February 11, 2011 12:53 PM
To: mysql@lists.mysql.com
Subject: Converting INNODB to file-per-table
Message-
From: Jan Steinman [mailto:j...@bytesmiths.com]
Sent: Friday, February 11, 2011 12:53 PM
To: mysql@lists.mysql.com
Subject: Converting INNODB to file-per-table?
Our incremental backups seem to be filling with instances of ib_logfile1,
ib_logfile2, and ibdata1.
I know that changing