Despite the conventional wisdom, converting to innodb_file_per_table will not
necessarily help you. It depends on your situation. If most of your growth is
in a single table, you will only have transferred the problem from the ibdata1
file to a new file. The ibdata1 file may also continue to
We have an application with blocks of code that begin with setting autocommit
off, and end with a commit. The code in between does only selects, no updating.
1) Am I correct in thinking that the autocommit and commit statements
don't really accomplish anything useful?
2) If the
To: Rozeboom, Kay [DAS]
Cc: mysql@lists.mysql.com
Subject: Re: Reusing ibdata1 space
- Original Message -
From: Kay Rozeboom [DAS] kay.rozeb...@iowa.gov
I realize that this would not return the unused space to the operating
system. But would it return it to MySQL so that it could
Thanks for the response, Johan.
It would really help if I could determine when the ballooning is occurring. Do
you know of any way to do that?
-Original Message-
From: Johan De Meersman [mailto:vegiv...@tuxera.be]
Sent: Thursday, November 17, 2011 1:28 AM
To: Rozeboom, Kay [DAS]
Cc
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
In the show table status output, there is comment field labeled InnoDB
free. Can someone explain what kind of free space is counted in this figure?
Is it space that is not currently part of any segment? Does it include empty
pages within segments? Does it include unused space within pages?
Thanks to everyone who replied to my question.
Kay Rozeboom
Information Technology Enterprise
Iowa Department of Administrative Services
Telephone: 515.281.6139 Fax: 515.281.6137
Email: kay.rozeb...@iowa.gov
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To
We are running MySQL 5.0.77, and using INNODB in production for the first time.
The production database has a lot of inserts and deletes, and the shared
ibdata1 file is continually growing. I understand that to return the unused
space to the operating system, we must delete and recreate
Does anyone know if this has been fixed yet?
-Original Message-
From: Jigal van Hemert [mailto:ji...@xs4all.nl]
Sent: Monday, September 26, 2011 2:02 PM
To: mysql@lists.mysql.com
Subject: Re: mysql listed as attach page by google?
Hi,
On 26-9-2011 20:30, Michael Albert wrote:
I don't
Hi,
I am new to MySQL and this listserv. I have a couple of questions about the
recommendations at the link given below.
1) If autocommit is turned off during the large load, could this cause the
underlying InnoDB log to grow too big?
2) If the unique checks and foreign key checks are
10 matches
Mail list logo