> > 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
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 set? If so, what is the co
I've been reading (and reading...) the innodb documentation about using the
innodb_file_per_table directive, and one thing still confuses me. If i use
this directive, then is it correct that the setting innodb_data_file_path
will specify the shared innodb information?
Also, when i create databas
