About MySQL Ddl_log.log file

A log file was found today in the data directory of the MySQL database

Ddl_log.log so the official website to see a bit, English good can read for themselves, bad on the trouble: (

The DDL Log

The DDL log, or metadata log, records metadata operations generated by data definition statements such asDROP TABLEandALTER TABLE. MySQL uses this log to recover from crashes occurring in the middle of a metadata operation. When executing the statementDROP TABLE t1, t2, we need to ensure that botht1andt2Is dropped, and the each table drop was complete. Another example of this type of SQL statement areALTER TABLE t3 DROP PARTITION p2, where we must make certain that the partition are completely dropped and that it definition is removed from the list of Partitions for tablet3.

A record of metadata operations such as those just described ddl_log.log is written to the file, in the MySQL data directory. T He is a binary file; It is not a intended to being human-readable, and you are should not the attempt to the modify its contents on any.

ddl_log.logis not created until it's actually needed for recording metadata statements, and is removed following a successful start Ofmysqld. Thus, it is possible for the this file isn't to being present on a MySQL server that's functioning in a completely normal manner.

Focus:

ddl_log.log  can to 1048573 entries, equivalent 4 GB in size. Once this limit was exceeded, you must rename or remove the file before it's possible to execute any additional DDL Statem Ents. This is a known issue which we be working to resolve (Bug #83708).

There is no user-configurable server options or variables associated with the this file.

This article is from "Shadow Knight" blog, please make sure to keep this source http://andylhz2009.blog.51cto.com/728703/1948981

About MySQL Ddl_log.log file