The MySQL team is proud to announce the general availability of version 8.0.24 of the MySQL Shell.

In addition to a considerable number of bugs fixed, the following changes were introduced.

Improved Command Line Integration

Integrating the shell functionality in DevOps operations is a key feature and this release has introduced a big improvement on this area being the most remarkable improvements the following:

• No longer need to execute APIs using the –execute (-e) command line argument: all of the data required for any API available in CLI can be defined through command line arguments (including lists).

Atomics (or GCC intrinsics) were first introduced in InnoDB (5.0) by a patch  from Mark Callaghan’s team at Google for mutexes and rw-locks. InnoDB code then was written in C.  When the code was ported to C++ ,  part of the 5.6 release, there was no C++ standard for atomics.…

The MySQL Development team is very happy to announce that MySQL 8.0.24 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.24 from dev.mysql.com or from the MySQL  Yum,  APT, or SUSE repositories.…

In this blog series, I’m describing how InnoDB locks data (tables and rows) in order to provide illusion to clients that their queries are executed one after another, and how this was improved in recent releases.

So far we saw that access right currently granted and waiting to be granted are represented as record locks and table locks objects in memory, which we can inspect via performance_schema.data_locks.…

In this blog series, I’m describing how InnoDB locks data (tables and rows) in order to provide illusion to clients that their queries are executed one after another, and how this was improved in recent releases.

As we’ve already seen, the order in which server pretends transactions are happening (the serialization order) is tied to the order in which locks are granted to transactions.…

In this  blog series, I’m describing how InnoDB locks data (tables and rows) in order to provide illusion to clients that their queries are executed one after another, and how this was improved in recent releases.
In InnoDB Data Locking – Part 1 “Introduction” I’ve introduced basic concepts required to understand current post:

• databases, tables, rows (like files on a shared drive, spreadsheets inside a file, and rows inside a spreadsheet)
• serializability of transactions (ability to explain states observed over time with a convincing story about relative order of parallel operations)
• timeouts (for misbehaving lock owners, and to resolve deadlocks)
• reader-writer lock (shared/exclusive access rights)
• starvation (permanent inflow of readers starving a writer waiting for its turn)
• queueing (FIFO, or priority)
• read views (read-only snapshots which allow stale reads concurrent to new writes)
• granularity of a lock (access right to everything vs.

The MySQL team is proud to announce the general availability of version 8.0.23 of the MySQL Shell.

In addition to a considerable number of bugs fixed, the following changes were introduced.

Improved Import Table

The importTable utility continues getting better, the following enhancements:

• Multiple file import: it is now supported to load a defined set of files into the same table, glob patterns can be used to determine the files to be loaded.

In MySQL Server 8.0.23 an improvement was made to InnoDB that allows truncation and deletion of all tablespaces to be faster. In fact, making it almost instantaneous as long as AHI is disabled. This is done by allowing pages in the buffer pool to be freed lazily instead of immediately when a tablespace is deleted.…