All together now
Let’s now put together all that we’ve learned in InnoDB Data Locking – Part 2 “Locks” about table and record locks to understand following situation:
Category Archives: MySQL
Auditing Changes to Classified Data Stored in MySQL 8.0
The Challenge
Often with sensitive information, you need to have an audit log. Frequently data such as this will contain a classification level as part of the row, defining policies for how it is handled, audited, etc. In a prior blog I discussed how to audit the selection of classified data.
… MySQL Audit Data Consolidation – Made Simple
In this blog, I am going to demonstrate how to create your own consolidated audit log archive across many mysql instances. In a followup I’ll show how to extend this example by creating a simple hash chain on that archive – so you can prove whether or not its been modified or tainted in any way and if so where.…
The MySQL 8.0.22 Maintenance Release is Generally Available
The MySQL Development team is very happy to announce that MySQL 8.0.22 is now available for download at dev.mysql.com. In addition to bug fixes there are a few new features added in this release. Please download 8.0.22 from dev.mysql.com or from the MySQL Yum, APT, or SUSE repositories.…
InnoDB Data Locking – Part 2 “Locks”
In InnoDB Data Locking – Part 1 “Introduction” we’ve described the difficulties Lock System tries to solve using metaphor of people trying to concurrently edit spreadsheets. While it might be useful metaphor to get some intuitions about the problem, to talk about solutions it helps to know at least a little about the “reality” this metaphor maps to.…
Auditing Selection of Classified Data Stored in MySQL 8.0
The Challenge
Often with sensitive information, you need to have an audit log. Not just that a table had a select run, but that specific cells within the table were accessed. Frequently data such as this will contain a classification level as part of the row, defining policies for how it is handled, audited, etc.
… InnoDB Data Locking – Part 1 “Introduction”
In this blog series, I’d like to introduce you gently to the topic on which I was working last 2 years, which is improving how InnoDB locks data (tables and rows) in order to provide illusion to clients that their queries are executed one after another, while in reality there is a lot of concurrency.…
MySQL Shell Dump & Load part 4: Dump Instance & Schemas
MySQL Shell 8.0.21 comes with two utilities which can be used to perform logical dumps of all the schemas from an instance (util.dumpInstance()) or selected schemas (util.dumpSchemas()). These tools offer major performance improvements over the mysqldump utility, some of our benchmarks show a throughput up to 3GB/s!…
New Consistency for Datafile Locations in MySQL 8.0.21
When you create a general tablespace in MySQL 8.0, you can choose the directory where the associated datafile is created.
CREATE TABLESPACE tablespace_name ADD DATAFILE ‘/my/table/space/dir’;
However, that directory must be known to InnoDB. Known directories are defined by the following settings: datadir, innodb_data_home_dir, innodb_undo_directory & innodb_directories.…
Improvements to Undo Truncation in MySQL 8.0.21
Undo Tablespaces can be truncated either implicitly or explicitly in MySQL 8.0. Both methods use the same mechanism. This mechanism could cause periodic stalls on very busy systems while an undo tablespace truncate completes. This problem has been fixed in MySQL 8.0.21.…