Atomic DDL in MariaDB

on YouTube ↗19m

" summary

MariaDB 10.6 implements atomic DDL by extending the existing DDL log (see MDEV-17567): operations write phase markers and a unique xid which is synced into the binary log, recovery scans binlog and DDL log to either roll back unfinished renames or finish/drop remaining objects. RENAME and DROP (tables, views, triggers, databases) are already supported; CREATE/ALTER work is next. Cost is modest but real — roughly six fsyncs per table for a full rename sequence.

AI-written summary · about

" chapters (11)

1. 0:00Start
2. 0:26A bit of MariaDB History
3. 2:32Problems with the "old" design
4. 4:08Functionality we want to keep
5. 4:48The solution
6. 6:21What will be done next
7. 10:17Implementation details for DROP TABLE Amic drop is depending on the force DROP TABLE code in 10.5
8. 11:57Implementation details for DROP DATABASE
9. 15:21Ideas about faster information schema tables
10. 16:39New data dictionary The idea is to not keep things compatible with how things are before
11. 18:30Questions?

" related talks

• 17mState of MariaDBMichael Widenius · Percona Live 2022
• 15mDDLumos: Understanding and Detecting Atomic DDL Bugs in DBMSsYu Jiang, Jie Liang, Zhiyong Wu, Jingzhou Fu, Wenqian Deng · USENIX ATC '25
• 53mMariaDB Server 10.2: The Complete GuideColin Charles · Percona Live Open Source Database Conference 2017
• 41mMariaDB The New MySQLColin Charles · HighLoad++ 2012
• 27mState of MariaDBMichael Widenius · O'Reilly MySQL Conference & Expo 2011
• 24mTips and Tricks for Migrating from Oracle to MariaDBAnders Karlsson · MariaDB OpenWorks 2023
• 25mThe future of databases: Combining operational and analytical data at massive scaleRob Hedgpeth · Big Data & AI Toronto 2021
• 29mEverything You Ever Wanted to Know About MariaDB Replication but Were Afraid to AskEdward Stoever · MariaDB OpenWorks 2023