> > but you don't know __when__ innodb_file_per_table was set!
> > So it's possible that many innodb tables actually reside in ibdata
> > [1-4].
> > Check your data directory to see the individual innodb files/tables
> > (*.ibd).
>
> This is true, and even on a fresh install that has always had
On Apr 26, 2006, at 3:54 AM, Dr. Frank Ullrich wrote:
Duzenbury, Rich wrote:
Hi all,
I've inherited an innodb database that is configured like:
innodb_file_per_table
innodb_data_file_path =
ibdata1:3000M;ibdata2:3000M;ibdata3:3000M;ibdata4:3000M:autoextend
Um, doesn't this allocate 12G that wi
Duzenbury, Rich wrote:
Hi all,
I've inherited an innodb database that is configured like:
innodb_file_per_table
innodb_data_file_path =
ibdata1:3000M;ibdata2:3000M;ibdata3:3000M;ibdata4:3000M:autoextend
Um, doesn't this allocate 12G that winds up being unused, since
innodb_file_per_table is se
In my experience, I see about a 2x increase in space required between
MyISAM and InnoDB. I believe this may be documented btw, check the
InnoDB section of the manual.
I have been using InnoDB for a couple years now on databases up to
180GB. InnoDB has been very robust and I have only once come a
Alvaro,
- Original Message -
From: "Alvaro Avello" <[EMAIL PROTECTED]>
To: "Heikki Tuuri" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, July 15, 2003 11:38 PM
Subject: Re: innodb file won't shrink
> -BEGIN PGP SIGNED MES
MAIL PROTECTED]>
|Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
|Sent: Tuesday, July 15, 2003 1:13 AM
|Subject: Re: innodb file won't shrink
|
|
|>-BEGIN PGP SIGNED MESSAGE-
|>Hash: SHA1
|>
|>There 's any chance that in the future every InnoDB ta
Walt,
- Original Message -
From: "walt" <[EMAIL PROTECTED]>
To: "Heikki Tuuri" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, July 14, 2003 11:56 PM
Subject: Re: innodb file won't shrink
> Heikki Tuuri wrote:
> >
>
&g
Alvaro,
- Original Message -
From: "Alvaro Avello" <[EMAIL PROTECTED]>
To: "Heikki Tuuri" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, July 15, 2003 1:13 AM
Subject: Re: innodb file won't shrink
Heikki Tuuri wrote:
>
> On September 15th, 2003 you will be able to put every InnoDB table into its
> own file. That should alleviate this kind of problem.
>
>
> Best regards,
>
> Heikki Tuuri
> Innobase Oy
> http://www.innodb.com
> Transactions, foreign keys, and a hot backup tool for MySQL
>
Steve,
- Original Message -
From: "Steve" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Thursday, July 10, 2003 11:24 PM
Subject: Re: innodb file won't shrink
> I found the following thread:
>
>
http://groups.google.com/gr
I.-A.,
- Original Message -
From: ""I-A.Kotopoulos"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Wednesday, June 25, 2003 10:05 AM
Subject: InnoDB file...
> --=_NextPart_000_00B5_01C33B01.642AD2C0
> Content-Type: text/plain;
> charset="Windows-1252"
> Content-Transf
>From the InnoDB manual:
Dropping a table or deleting all rows from it is guaranteed to release the space
to other users, but remember that deleted rows can be physically removed only in
a purge operation after they are no longer needed in transaction rollback or
consistent read.
Perhaps that help
Yes, I saw that before...My filesize was limited to 2GB before, but now with
a 2.4 kernel and reiserfs I _should_ be allowed to create a 20GB data file
now, right?
So something's wrong... as I said before, I have successfully created a 9GB
file on this machine before, so the filesystem isn't to b
://www.mysql.com
-Original Message-
From: Gurupartap Davis <[EMAIL PROTECTED]>
To: Heikki Tuuri <[EMAIL PROTECTED]>; [EMAIL PROTECTED]
<[EMAIL PROTECTED]>
Date: Saturday, February 09, 2002 2:32 AM
Subject: Re: InnoDB File Size
>Yes, I saw that before...My filesize was limited t
Hi!
>From http://www.innodb.com/ibman.html :
MySQL/InnoDB-3.23.44, November 2, 2001
You can define foreign key constraints on InnoDB tables. An example: FOREIGN
KEY (col1) REFERENCES table2(col2).
You can create > 4 GB data files in those file systems that allow it.
Thus > 4 G files
://www.mysql.com
-Original Message-
From: Gurupartap Davis <[EMAIL PROTECTED]>
To: Heikki Tuuri <[EMAIL PROTECTED]>; [EMAIL PROTECTED]
<[EMAIL PROTECTED]>
Date: Saturday, February 09, 2002 2:32 AM
Subject: Re: InnoDB File Size
>Yes, I saw that before...My filesize was limited t
On Friday 08 February 2002 16:32, Gurupartap Davis wrote:
> Yes, I saw that before...My filesize was limited to 2GB before, but now
> with a 2.4 kernel and reiserfs I _should_ be allowed to create a 20GB
> data file now, right?
>
> So something's wrong... as I said before, I have successfully crea
Yes, I saw that before...My filesize was limited to 2GB before, but now with
a 2.4 kernel and reiserfs I _should_ be allowed to create a 20GB data file
now, right?
So something's wrong... as I said before, I have successfully created a 9GB
file on this machine before, so the filesystem isn't to b
Hi!
>From http://www.innodb.com/ibman.html :
MySQL/InnoDB-3.23.44, November 2, 2001
You can define foreign key constraints on InnoDB tables. An example: FOREIGN
KEY (col1) REFERENCES table2(col2).
You can create > 4 GB data files in those file systems that allow it.
Thus > 4 G files
> In the last episode (Nov 02), Stephen Lee said:
>> I have the following settings in /etc/my.cnf:
>>
>> default-table-type=innodb
>> innodb_data_file_path = ibdata1:1000M
>> set-variable = innodb_log_file_size=5M
>>
>> The resulting files:
>> -rw-rw1 mysqlmysql2560 Nov 2 12:1
In the last episode (Nov 02), Stephen Lee said:
> I have the following settings in /etc/my.cnf:
>
> default-table-type=innodb
> innodb_data_file_path = ibdata1:1000M
> set-variable = innodb_log_file_size=5M
>
> The resulting files:
> -rw-rw1 mysqlmysql2560 Nov 2 12:17 ib_arc
Hi,
> how much of the 600MB actually is used at the moment
I'm sure there'a a better way to do it, but this one works:
mysql> show table status like 'your_innodb_table' \G
...
Comment: InnoDB free: 3739648 kB
Best Regards,
Sasa
-
22 matches
Mail list logo
