17.7.2.3 Consistent Nonlocking Reads| dev.mysql.com
7.1.7 Server Command Options| dev.mysql.com
So I’m a huge SQLite fanboy and I use it for almost everything these days. Recently, the project added sqlite3_rsync which allows you to swiftly replicate your database to other servers (or to the same server if you want), and this really was the cherry on top for me. Last week however, I ran into one of my projects unexpectedly getting SQLITE_BUSY errors. And then someone urged me to run ‘a real database’ (PostgreSQL), and that hurt.| Bert Hubert's writings
6.5.4 mysqldump — A Database Backup Program| dev.mysql.com
15.3.1 START TRANSACTION, COMMIT, and ROLLBACK Statements| dev.mysql.com
7.1.8 Server System Variables| dev.mysql.com
innodb_adaptive_flushing| dev.mysql.com
Whenever updating a few records in an OLTP table we just use the update command. But what if we have to update millions of records in an OLTP table? If you run a large update, your database will lock those records and other transactions may fail. In this post we look at how a large update can cause lock timeout error and how running batches of smaller updates can eliminate this issue.| www.startdataengineering.com