This article introduces Panda Index, PolarDB-X's native multi-version unique key index that eliminates gap-lock contention and table-lookup visibility checks.
This article introduces PolarDB-X's Secondary Prefix Compression (SPC), which shrinks secondary indexes by up to 70% to boost I/O performance.
This article introduces Alibaba Cloud PolarStore's software-hardware collaborative compression architecture for cloud-native databases, which received a Best Paper Award nomination at USENIX FAST'26.
Claude Code Rewrites PostgreSQL: Full Page Write vs. MySQL Doublewrite Buffer, 3× Performance Difference
This article debunks the outdated MySQL 5M-row single-table limit myth, explaining how modern B+Tree architecture and hardware make large tables fully viable.
This article introduces why MySQL B-tree height stays within 4–5 layers even with tens of billions of rows, debunking the myth that single tables must be sharded after 5 million rows.
This article introduces PostgreSQL's blink-tree implementation for high-concurrency B-tree operations using link pointers and optimized locking mechanisms.
The article explains DuckDB’s HyPer-inspired MVCC design, which uses transaction IDs and timestamps for simple, efficient visibility checks without read views.
This article examines the isolation levels supported by InnoDB, explores how locks are acquired during data insertion, deletion, modification, and query operations.
This article describes the basic usage, effects, principles, and restrictions of the parallel acceleration technologies provided by MySQL at the InnoDB layer.
This article introduces the concurrent access control features of MySQL database systems, specifically focusing on page-level and row-level concurrent access control.
This article aims to focus on the core functionalities of the Buffer Pool, providing an introduction to its interfaces, memory organization, page retrieval, and flushing.
This article introduces the structure and usage of InnoDB memory. The code is based on version 8.0.25.
This article introduces the memory allocation manager at the InnoDB layer and the SQL layer, including ut_allocator, mem_heap_allocator, and MEM_ROOT.
This article interprets the MySQL memory limit feature. The code is based on version 8.0.28.
This article introduces Undo Log in InnoDB, including its role, design ideas, record content, organizational structure, and various functional implementations.
This article will focus on several aspects of REDO logs, including the role, recorded content, organizational structure, and writing methods.
This article focuses on the data structure and implementation architecture of the data dictionary.
If you have no idea about InnoDB, you can read another article on InnoDB, including the transaction subsystem, transaction lock, redo log, undo log, and crash recovery logic of InnoDB.
In this blog, we will talk about Alibaba Cloud's new relational database service: ApsaraDB for MariaDB TX, its features, and its advantages.
