#innodb — Public Fediverse posts

Deploy a complete MySQL 8.0 InnoDB Cluster for high availability with a single command using MySQL Shell's AdminAPI. Automates Group Replication across three nodes, handling member auto-joining, failure detection, and distributed recovery. Shared-nothing architecture with automatic primary election. #mysql #innodb-cluster #ValtersIT

https://www.valtersit.com/vault/mysql-80-innodb-cluster-full-deployment-automation-f25fe5/

https://blog.gslin.org/archives/2026/05/23/13044/innodb-%e7%9a%84-repeatable-read-%e8%88%87-next-key-lock-%e7%9a%84%e9%97%9c%e4%bf%82/

InnoDB 的 REPEATABLE READ 與 next-key lock 的關係

#db #innodb #key #lock #mysql #next #performance #phantom #query #range #rdbms #read #repeatable #row #speed #sql #transaction

https://blog.gslin.org/archives/2026/05/23/13044/innodb-%e7%9a%84-repeatable-read-%e8%88%87-next-key-lock-%e7%9a%84%e9%97%9c%e4%bf%82/

InnoDB 的 REPEATABLE READ 與 next-key lock 的關係

#db #innodb #key #lock #mysql #next #performance #phantom #query #range #rdbms #read #repeatable #row #speed #sql #transaction

[Перевод] MariaDB 12.3: binlog внутри InnoDB

Коротко для ленивых В MariaDB 12.3 binlog можно хранить внутри InnoDB через binlog_storage_engine=innodb . Главный эффект: вместо двух fsync() на commit остаётся один, поэтому на write-heavy нагрузке резко растут TPS и снижается tail latency. В тестах из статьи прирост на полном durability-профиле составил примерно 2.4x–3.3x . Backup, restore и ресинк реплик становятся проще, потому что binlog и данные теперь консистентны на уровне одного механизма хранения. Цена за это: обязателен GTID, Galera пока не поддерживается, а innodb_log_file_size нужно подбирать внимательнее из-за роста объёма redo. Если у вас обычная схема primary + async replica на InnoDB, эту возможность точно стоит хотя бы протестировать.

https://habr.com/ru/articles/1011298/

#MariaDB_123 #InnoDB #binlog #GTID #репликация #производительность_SQL #crash_recovery #fsync #OLTP

https://blog.gslin.org/archives/2026/02/21/12901/mariadb-12-3-%e5%b0%8d-innodb-%e7%9a%84%e5%a4%a7%e6%94%b9%e9%80%b2/

MariaDB 12.3 對 InnoDB 的大改進

#binlog #cpu #database #db #engine #fsync #i/o #innodb #latency #mariadb #mysql #performance #rdbms #speed #storage #write

https://blog.gslin.org/archives/2026/02/21/12901/mariadb-12-3-%e5%b0%8d-innodb-%e7%9a%84%e5%a4%a7%e6%94%b9%e9%80%b2/

MariaDB 12.3 對 InnoDB 的大改進

#binlog #cpu #database #db #engine #fsync #i/o #innodb #latency #mariadb #mysql #performance #rdbms #speed #storage #write

In the tests in my previous articles, I found that #MariaDB completely ruined the concept of the dynamically configurable #InnoDB buffer pool!

And this within a long-term support release series. To prevent this from affecting your production environment, I have described more about this here:

https://www.fromdual.com/blog/mariadb-dynamically-configurable-buffer-pool-broken/

Image Author: Cplakidas, GNU FDL v1.2

Bei den Tests in meinen vorherigen Artikeln habe ich festgestellt, dass #MariaDB das Konzept des dynamisch konfigurierbaren #InnoDB Buffer Pools völlig kaputt gemacht hat!

Und dies innerhalb einer Long-Term-Support Release-Reihe. Mehr dazu, damit Euch das nicht in der Produktion auf die Füsse fällt, habe ich hier beschrieben:

https://www.fromdual.com/de/blog/mariadb-dynamisch-konfigurierbare-buffer-pool-kaputt/

Image Author: Cplakidas, GNU FDL v1.2

New binlog implementation in MariaDB 12.3. Vastly improved performance by default, and crash-safe for those who had performance configs. https://mariadb.org/new-binlog-implementation-in-mariadb-12-3/ #mariadb #opensource #database #innodb

New binlog implementation in MariaDB 12.3. Vastly improved performance by default, and crash-safe for those who had performance configs. https://mariadb.org/new-binlog-implementation-in-mariadb-12-3/ #mariadb #opensource #database #innodb

At least some of the senior #PostgreSQL experts have identified the weak spots: "What's Missing in Postgres?" by Bruce Momjian: https://momjian.us/main/writings/pgsql/missing.pdf
That is a good starting point for improvement.
IMHO their outdated MVCC implementation is still missing from this presentation. And #InnoDB index clustered tables are really cool!

At least some of the senior #PostgreSQL experts have identified the weak spots: "What's Missing in Postgres?" by Bruce Momjian: https://momjian.us/main/writings/pgsql/missing.pdf
That is a good starting point for improvement.
IMHO their outdated MVCC implementation is still missing from this presentation. And #InnoDB index clustered tables are really cool!

This MySQL setting makes your PHP app dead slow or crazy fast

https://phpc.tv/w/2c84XvxLrthseySG9L6WRn

This MySQL setting makes your PHP app dead slow or crazy fast

https://phpc.tv/w/2c84XvxLrthseySG9L6WRn

sort of interesting to see the opcache built right in

PHP 8.3.29 (cli) (built: Dec 18 2025 23:21:17) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.3.29, Copyright (c) Zend Technologies
with Zend OPcache v8.3.29,

the way to 400gb db and 30gb indexes is 512gb ram - served all from the memory #4x128 #innodb buffer pool

sort of interesting to see the opcache built right in

PHP 8.3.29 (cli) (built: Dec 18 2025 23:21:17) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.3.29, Copyright (c) Zend Technologies
with Zend OPcache v8.3.29,

the way to 400gb db and 30gb indexes is 512gb ram - served all from the memory #4x128 #innodb buffer pool

Транзакции в InnoDB: разбираемся с уровнями изоляции и блокировками

Чтобы транзакции в InnoDB работали предсказуемо, важно понимать внутреннюю логику InnoDB. Ошибки чаще всего возникают не из-за отсутствия транзакций, а из-за неверных ожиданий относительно уровней изоляции и работы блокировок. В этой статье давайте разберём несколько распространенных заблуждений и на примерах посмотрим, как на самом деле работают транзакции.

https://habr.com/ru/companies/rusprofile/articles/969954/

#innodb #transaction #уровни_изоляции #блокировки

I finally finished this upgrade this morning. There was a new check that I had to fiddle around with to get working and then of course #Nomad wanted to battle with me. And then that was all on top of #InnoDB being rude as well! :derpfuuu:

#GitHubEnterprise #GitHub #GHE #life #busy #Linux #git :github1: :linux: :mysql1:

I finally finished this upgrade this morning. There was a new check that I had to fiddle around with to get working and then of course #Nomad wanted to battle with me. And then that was all on top of #InnoDB being rude as well! :derpfuuu:

#GitHubEnterprise #GitHub #GHE #life #busy #Linux #git :github1: :linux: :mysql1:

I've started a mini #MySQLShorts series on #InnoDB History List Length, don't miss the first episode! https://www.youtube.com/watch?v=_LMsG4RWfMk&list=PLWx5a9Tn2EvG4C90YFJ9eU61IpALeE0SN&index=97 #MySQLCommunity

I've started a mini #MySQLShorts series on #InnoDB History List Length, don't miss the first episode! https://www.youtube.com/watch?v=_LMsG4RWfMk&list=PLWx5a9Tn2EvG4C90YFJ9eU61IpALeE0SN&index=97 #MySQLCommunity

Deepintodev.com reviews how modern database storage engines store, retrieve, and update database table rows on memory and disk. This serves as a foundation to understanding how indexes and clustered indexes work, the concerned data structures, and their use cases; these are reviewed as well.

"How Databases Store Your Tables on Disk"

https://www.deepintodev.com/blog/how-databases-store-your-tables-on-disk

#programming #databases #memory #postgresql #mysql #innodb

Deepintodev.com reviews how modern database storage engines store, retrieve, and update database table rows on memory and disk. This serves as a foundation to understanding how indexes and clustered indexes work, the concerned data structures, and their use cases; these are reviewed as well.

"How Databases Store Your Tables on Disk"

https://www.deepintodev.com/blog/how-databases-store-your-tables-on-disk

#programming #databases #memory #postgresql #mysql #innodb

Today I hate #InnoDB fragmentation, and incompatible #crontab files across different versions of #cron

Today I hate #InnoDB fragmentation, and incompatible #crontab files across different versions of #cron

[小ネタ] MySQL (InnoDB) でユニットテスト最中のDBを外部から見たい場合は READ UNCOMMITTED を使うといいかも
https://qiita.com/ssc-ksaitou/items/25a6a7c5510d252b9e16?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items

#qiita #MySQL #unittest #InnoDB #ユニットテスト

https://blog.martinscloud.com/mysql-deploy-innodb-clusterset/ #oracle #mysql #innodb

https://blog.martinscloud.com/mysql-deploy-innodb-clusterset/ #oracle #mysql #innodb

https://blog.martinscloud.com/mysql-configure-innodb-replicaset-2/ #mysql #innodb #cluster

https://blog.martinscloud.com/mysql-configure-innodb-replicaset-2/ #mysql #innodb #cluster

https://blog.martinscloud.com/mysql-create-an-innodb-cluster/ #oracle #mysql #innodb #cluster

https://blog.martinscloud.com/mysql-create-an-innodb-cluster/ #oracle #mysql #innodb #cluster

https://blog.martinscloud.com/use-docker-compose-for-mysql/ #mysql #oracle #innodb #docker #compose #docker_compose

https://blog.martinscloud.com/use-docker-compose-for-mysql/ #mysql #oracle #innodb #docker #compose #docker_compose

2/ 🛠️ Switch to a Modern Storage Engine

Consider switching your database storage engine to InnoDB if you haven't already. InnoDB supports row-level locking and transactions, making it ideal for high-concurrency environments typical in busy online stores. #DatabaseOptimization #InnoDB

2/ 🛠️ Switch to a Modern Storage Engine

Consider switching your database storage engine to InnoDB if you haven't already. InnoDB supports row-level locking and transactions, making it ideal for high-concurrency environments typical in busy online stores. #DatabaseOptimization #InnoDB

Dealing with MySQL Lock Timeouts: Bail faster. #MySQL #InnoDB #Shopware

https://tideways.com/profiler/blog/dealing-with-mysql-lock-timeouts-bail-faster?utm_source=flipboard&utm_medium=activitypub

Posted into SYMFONY FOR THE DEVIL @symfony-for-the-devil-mobileatom

Optimizing MariaDB
MariaDB is a versatile and powerful database management system. To get the best performance, you need to optimize it according to your specific use case. In this post, we will provide detailed examples…
https://linuxexpert.org/optimizing-mariadb/

#mariadb #mysql #linux #innodb #dbms

InnoDB Performance Tuning – 11 Critical InnoDB Variables to Optimize Your MySQL Database. #InnoDB #MySQL

https://dev.to/drupaladmin/innodb-performance-tuning-11-critical-innodb-variables-to-optimize-your-mysql-database-2l01?utm_source=flipboard&utm_medium=activitypub

Posted into SYMFONY FOR THE DEVIL @symfony-for-the-devil-mobileatom

All you need to know about MySQL InnoDB Primary Keys, session recorded at @GroningenPHP https://buff.ly/3VBFFnP #MySQL #InnoDB #Meetup #MySQLCommunity

All you need to know about MySQL InnoDB Primary Keys, session recorded at @GroningenPHP https://buff.ly/3VBFFnP #MySQL #InnoDB #Meetup #MySQLCommunity

MySQL 8.4 LTS – new production-ready defaults for InnoDB
Yesterday, MySQL 8.4, the very first LTS version of MySQL was released.

A lot of deprecations have finally been removed, and several InnoDB variable default values have been modified to match current workloads and hardware specifications.

The default value of 20 InnoDB variables has been modified!

Let's have a look
https://lefred.be/content/mysql-8-4-lts-new-production-ready-defaults-for-innodb/
#84 #InnoDB #LTS #MySQL

MySQL 8.4 LTS – new production-ready defaults for InnoDB
Yesterday, MySQL 8.4, the very first LTS version of MySQL was released.

A lot of deprecations have finally been removed, and several InnoDB variable default values have been modified to match current workloads and hardware specifications.

The default value of 20 InnoDB variables has been modified!

Let's have a look
https://lefred.be/content/mysql-8-4-lts-new-production-ready-defaults-for-innodb/
#84 #InnoDB #LTS #MySQL

MySQL InnoDB’s Instant Schema Changes: What DBAs Should Know
In MySQL 8.0.12, we introduced a new algorithm for DDLs that won't block the table when changing its definition. The first instant operation was adding a column at the end of a table, this was a contribution from Tencent Games.

Then in MySQL 8.0.29 we added the possibility to add (or remove) a column anywhere
https://lefred.be/content/mysql-innodbs-instant-schema-changes-what-dbas-should-know/
#80 #InnoDB #MySQL #MySQL80

MySQL InnoDB’s Instant Schema Changes: What DBAs Should Know
In MySQL 8.0.12, we introduced a new algorithm for DDLs that won't block the table when changing its definition. The first instant operation was adding a column at the end of a table, this was a contribution from Tencent Games.

Then in MySQL 8.0.29 we added the possibility to add (or remove) a column anywhere
https://lefred.be/content/mysql-innodbs-instant-schema-changes-what-dbas-should-know/
#80 #InnoDB #MySQL #MySQL80

MySQL InnoDB: Primary Key always included in secondary indexes as the right-most columns… or not
Recently during the Swedish MySQL User Group (SMUG), I presented a session dedicated to MySQL InnoDB Primary Keys.

I forgot to mention a detail that many people are not aware, but Jeremy Cole has pointed out.

Primary Key always included in secondary
https://lefred.be/content/mysql-innodb-primary-key-always-included-in-secondary-indexes-as-the-right-most-columns-or-not/
#InnoDB #MySQL

MySQL InnoDB: Primary Key always included in secondary indexes as the right-most columns… or not
Recently during the Swedish MySQL User Group (SMUG), I presented a session dedicated to MySQL InnoDB Primary Keys.

I forgot to mention a detail that many people are not aware, but Jeremy Cole has pointed out.

Primary Key always included in secondary
https://lefred.be/content/mysql-innodb-primary-key-always-included-in-secondary-indexes-as-the-right-most-columns-or-not/
#InnoDB #MySQL

The reliability studies are particularly damning, they show #MySQL/#MariaDB's #InnoDB loses the entire database after a system crash on every workload tested. https://lists.openldap.org/hyperkitty/list/[email protected]/message/K5XMXFFGHQOWKB6G2UGHWHW5WVH7X77C/

(Note that they claimed to have found 1 flaw in #LMDB that occurred in 0.05% of their test runs, but it was actually a bug in the ext3 fs driver. One that had been fixed in Linux 2+ years before they began their research. In fact LMDB's reliability is flawless.) LMDB is the only DB that is perfectly crash-proof.

The reliability studies are particularly damning, they show #MySQL/#MariaDB's #InnoDB loses the entire database after a system crash on every workload tested. https://lists.openldap.org/hyperkitty/list/[email protected]/message/K5XMXFFGHQOWKB6G2UGHWHW5WVH7X77C/

(Note that they claimed to have found 1 flaw in #LMDB that occurred in 0.05% of their test runs, but it was actually a bug in the ext3 fs driver. One that had been fixed in Linux 2+ years before they began their research. In fact LMDB's reliability is flawless.) LMDB is the only DB that is perfectly crash-proof.

So while he's doing extra administrative work (fine tuning to search for safe memory allocation parameters) he's getting orders of magnitude slower performance using #InnoDB than #LMDB, and none of the crash reliability that he claims to value.
http://www.lmdb.tech/bench/memcache/

So while he's doing extra administrative work (fine tuning to search for safe memory allocation parameters) he's getting orders of magnitude slower performance using #InnoDB than #LMDB, and none of the crash reliability that he claims to value.
http://www.lmdb.tech/bench/memcache/