This article series introduces everything you need to know about database kernel, including Join elimination, Metadata Lock (MDL) management, query pruning, and more.
This article describes the design of the basic components of the row-column fusion execution architecture of PolarDB.
This article uses the join reorder of Polar DB MySQL In-Memory Column Index (IMCI) to describe the query optimization process of PolarDB HTAP.
This article aims to answer one question – what happens to distributed databases when two machines are hung up? – (with examples).
This article describes the query pruning technology of PolarDB IMCI.
This article introduces a method that utilizes the capabilities of window aggregate functions to decorrelate subqueries.
This article describes a heuristic query transformation implemented by PolarDB called join elimination.
This article introduces the concept of join condition pushdown of query transformation in database optimization.
This article provides an overview of the experience and progress in end-to-end Metadata Lock (MDL) lock management in Alibaba Cloud PolarDB.
This article focuses on the IN-list transformation of PolarDB, which showcases the query rewriting capabilities of PolarDB.
This article describes the definition of predicate pushdown and why databases should perform predicate pushdown.
This article describes traditional database and data warehouse solutions and delves into the technical aspects of PolarDB's IMCI columnar JSON.
This article introduces the performance impact of using OSS as the underlying storage medium for X-Engine and discusses its suitability for different query scenarios.
This article describes the specific optimizations from the perspective of the core benefits of PolarDB for MySQL's IMCI Serverless feature.
This article introduces the Lizard SCN standalone transaction system of PolarDB-X Storage Engine in depth.
This article introduces the Lizard GCN distributed transaction system of PolarDB-X Storage Engine in depth.
This article provides a detailed overview of the evolution of PolarDB for MySQL from its initial development to its current state.
5 923 0
5 2402 1
8 3416 2
17 6955 3
9 3342 1
10 3525 1
