[Info-vax] Databases versus RMS

[Arne Vajhøj]

On 4/22/2012 1:30 AM, JF Mezei wrote:
> Arne Vajhøj wrote:
>
>> With InnoDB tables you only have a few files for the entire
>> database no matter how many tables.
>
> This is what I get with only 1 database and 3 tables.  those
> mysql-bin.xxxxxxx files seems to contain the data. the "bike" database
> conftains what seems to be just the table definitions (.frm files)
>
>> velo:mysql $  ls
>> bike                    mysql-bin.000005        mysql-bin.000014        mysql-bin.000023        mysql-bin.index
>> ib_logfile0             mysql-bin.000006        mysql-bin.000015        mysql-bin.000024        mysql.sock
>> ib_logfile1             mysql-bin.000007        mysql-bin.000016        mysql-bin.000025        mysql_service.log
>> ibdata1                 mysql-bin.000008        mysql-bin.000017        mysql-bin.000026        mysql_upgrade_info
>> mysql                   mysql-bin.000009        mysql-bin.000018        mysql-bin.000027        performance_schema
>> mysql-bin.000001        mysql-bin.000010        mysql-bin.000019        mysql-bin.000028        velo.vaxination.ca.pid
>> mysql-bin.000002        mysql-bin.000011        mysql-bin.000020        mysql-bin.000029
>> mysql-bin.000003        mysql-bin.000012        mysql-bin.000021        mysql-bin.000030
>> mysql-bin.000004        mysql-bin.000013        mysql-bin.000022        mysql-bin.000031
>>
>> velo:mysql $
>
>
> Until  I understand how it uses those files and how the data is
> organised between the multiple files, I can't claim to understand enough
> of this database system to support a production one.

The InnoDB data are in ibdata1.

The InnoDB log is in ib_logfile*.

The MySQL replication log is in mysql-bin.*.

Using MySQL replication log is optional.

I would seriously consider moving the InnoDB data and log to another dir
than the MySQL software tree.

Have you read the MySQL documentation?

Arne