![]() On a replica, it is theĭifference of the end execution time on the replica minus theīeginning execution time on the source. Indicates which thread executed the event.Įxec_time is the time spent executing theĮvent, on a replication source server. Indicates where the next event starts (that is, it is the end Replication, this timestamp is propagated to replica servers. Statement started on the server where the event originated. The second line starts with a date and time indicating when the Indicates the file offset, or starting position, of the event in In the first line, the number following at Query thread_id=3350 exec_time=11 error_code=0 See Section 17.2.1, “Replication Formats”, forĮvents are preceded by header comments that provide additional Row-based logging, the event indicates a row change rather thanĪn SQL statement. Statement was executed, how much time it took, and so forth. ![]() Server on which it was executed, the timestamp when the For statement-based logging,Įvent information includes the SQL statement, the ID of the Section 17.2.4, “Relay Log and Replication Metadata Repositories”.įor example, to display the contents of the binary log fileīinlog.000003. Theīinary log and relay log are discussed further in Log files written by a replica server in a replication setupīecause relay logs have the same format as binary logs. Mysqlbinlog to display the contents of relay Toĭisplay their contents in text format, use the The server writes these files in binary format. “ events” that describe modifications to databaseĬontents. ![]() The server's binary log consists of files containing 4.6.9.1 mysqlbinlog Hex Dump Format 4.6.9.2 mysqlbinlog Row Event Display 4.6.9.3 Using mysqlbinlog to Back Up Binary Log Files 4.6.9.4 Specifying the mysqlbinlog Server ID
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |