Speaker: Shipra Jain
Info: https://2018.fossasia.org/event/speakers.html#shipra-jain3274

Up till MySQL 5.7 version, DDL statement execution is non-atomic which caused many issues with respect to DDL crash safeness and slave drift in replication setup. New transactional Data-dictionary implementation in the MySQL 8.0  helped in making the DDL statements atomic in MySQL 8.0.

"Now DDL is atomic  in MySQL 8.0"

An atomic DDL statement combines the data dictionary updates, storage engine operations, and binary log writes associated with a DDL operation into a single, atomic transaction. The transaction is either committed, with applicable changes persisted to the data dictionary, storage engine, and binary log, or is rolled back, even if the server halts during the operation.

With this new implementation in MySQL have eliminated possibilities for internal consistencies in the server and SE after crash. Also in a replicated environment this is especially important since the probability for slave drift caused by crashes during execution of DDL on master/slave is eliminated.

============== 

What is  atomic DDL ?

What improvement atomic DDL gets to the user ?

What helped in implementing atomic DDL ?

Supported DDL Statements.

Changes in DDL Statement Behavior.

Storage Engine Support.

Viewing DDL Logs.

Track: Database
Room: Training room 2-1
Date: Sunday, 25th March, 2018

Event Page: http://2018.fossasia.org
Follow FOSSASIA on Twitter: https://twitter.com/fossasia/
Like FOSSASIA on Facebook: https://www.facebook.com/fossasia/

Produced by Engineers.SG