Analysis of physical file composition in MySql architecture

Because MySQL is the current IT industry's most popular, open source, and support multi-threaded high concurrency multi-user relational database management system, (in fact, is not the opportunity to contact other databases), so recently ready to start from the beginning to the bottom, a good study of MySQL, including MySQL basic introduction, Performance Tuning and architecture design, of course, only theoretical knowledge is certainly not enough, these things, must be combined with the actual operation, to slowly grasp, this is a time of accumulation, I just first to learn the theoretical knowledge, for the actual operation in the future under preparation,

So the recent will be published some of my study summary, if you can get the great God's guidance, I would appreciate

Log file:

Error log:
Turn on the "-log–error" option on MySQL startup to record serious warnings and errors during MySQL run, and start/close information, files are stored in the data directory, Hostname.err

Binary log (Binary log & Binary log Index)
Open with "–log-bin[=file_name]" to record all query, and the details of each query execution time, resource usage, etc., and the file is stored in the data directory, mysql_bin.* (* represents 0-9)

Update log:
Similar to binary log,mysql5.0 no longer supported

Query log:
What's the difference between all query (and binary log) using the "–log[=file_name" record? , because it contains all of the Select, large size, affect performance, unless tracking specific SQL performance issues can be briefly opened, otherwise not recommended to open, stored in the data directory, Hostname.log

Slow query logs (slow query log):
With "–log-slow-queried[=file_name]" open, record execution time of query, file storage data directory, Hostname-slow.log

Innodb's online Redo log (Innodb Redo logs):
Record InnoDB all physical changes to my transaction information to ensure INNODB transaction security

Data files:
". frm" file
Table-related metadata (meta), such as table structure definition information, is available for all storage engines

". MyD" File
MyISAM storage engine unique, storing table data

". Myi" File
MyISAM storage engine unique, table index related information

". ibd" Files and Ibdata files
Store InnoDB data and index, exclusive tablespace as ". ibd" file, share tablespace as "ibdata" file

Replication Related Documents
Master.info file
Store in the slave-end data directory, record the master information of the slave, such as host address, link user, password, etc.

Relay Log & Relay log Index:
The Mysql-relay-bin.xxxxxn file is used to store the binary log information that the I/O thread on the slave is reading from the master, and then
The slave-end SQL thread reads and parses the corresponding log information from the relay log, converts it to the SQL statement executed by master, and then applies it to the slave end.

The Mysql-relay-bin.index file is similar to the Mysql_bin.index file and records the absolute path of the log storage file

Relay-log.info file:
Similar to Master.info, storing information written to the local relay log via slave I/O threads for slave-side SQL threads and certain management operations to obtain the current replication information at any time

Other File
My.cnf
MySQL system configuration Ask price, Windows is generally located in the "c:/windows" directory, unix/linux Default in the "/etc" directory

PID File
Process files, storing process IDs

Socket file
Unix/linux environment only, users in this environment without TCP/IP network directly using UNIX socket link MySQL