Tagged articles
EXPLAIN ANALYZE
11 articles · Page 1 of 1
This article analyzes why MySQL LIMIT with large offsets causes severe performance degradation, explaining the server-layer mechanics of OFFSET, comparing index-scan vs full-table-scan execution paths, and demonstrating two optimization techniques — delayed join (covering index subquery) and cursor-based pagination — with benchmark results showing 4.68s reduced to 0.21s and 0.006s respectively on a 1.28M-row table.
Covering IndexCursor PaginationDeep Pagination
0 likes · 17 min read

This guide details a systematic approach to MySQL index optimization: verify slow queries using performance_schema and system metrics, prove access paths with EXPLAIN ANALYZE, create indexes with rollback strategies using ALGORITHM=INPLACE and LOCK=NONE, address deep pagination with keyset pagination and N+1 queries with batch loading, and validate improvements with latency percentiles and lock metrics.
EXPLAIN ANALYZEIndex OptimizationInnoDB
0 likes · 12 min read

The article walks through a systematic MySQL 8.0 index‑optimization workflow—starting with diagnosing slow queries and lock waits, validating execution plans with EXPLAIN ANALYZE, safely adding or dropping indexes using online DDL, handling pagination patterns, and verifying improvements via comprehensive metrics before and after.
EXPLAIN ANALYZEIndex OptimizationMySQL
0 likes · 12 min read

When a core order‑query suddenly slowed from milliseconds to seconds, the team discovered that using PostgreSQL’s EXPLAIN ANALYZE revealed hidden plan regressions, outdated statistics, and index misuse, leading to a systematic, production‑grade methodology for diagnosing and fixing query performance issues.
EXPLAIN ANALYZEPerformance TroubleshootingPostgreSQL
0 likes · 32 min read


21CTOOct 7, 2025 · Databases
PostgreSQL 18, released on September 25 2025, introduces developer‑focused features such as native UUID v7 generation, virtual generated columns, enhanced RETURNING clauses, automatic BUFFERS in EXPLAIN ANALYZE, and a unified pg_get_acl() permission function, all aimed at improving everyday database development.
Database DevelopmentEXPLAIN ANALYZEPostgreSQL
0 likes · 8 min read

This article explains how MySQL's EXPLAIN and EXPLAIN ANALYZE statements work, compares their outputs, and demonstrates through three practical examples how to interpret actual execution costs, row counts, and loop information to identify indexing and query‑plan inefficiencies.
EXPLAINEXPLAIN ANALYZEMySQL
0 likes · 11 min read

This article explains how to use Flame Graphs to visualize MySQL execution plans, discusses the limitations of traditional EXPLAIN output, introduces the EXPLAIN ANALYZE feature in MySQL 8.0, provides sample SQL and command‑line usage, and shows how the visual tool helps quickly identify performance bottlenecks.
EXPLAIN ANALYZEFlame GraphMySQL
0 likes · 11 min read

This article summarizes MySQL 9.0’s new VECTOR column type, inline and implicit foreign‑key constraints, JSON EXPLAIN ANALYZE storage, prepared event statements, performance‑schema variable tables, enhanced EXPLAIN output, LIMIT 1 subquery support, as well as deprecated and removed features with practical examples.
Deprecated featuresEXPLAIN ANALYZEInline foreign key
0 likes · 13 min read

This guide introduces MySQL 8's Explain Analyze tool, demonstrates how to prepend EXPLAIN ANALYZE to a query, interprets its detailed output—including cost, actual time, rows, and loops—using a sample query on the Sakila database, and provides steps to set up the test environment.
EXPLAIN ANALYZEMySQLQuery Performance
0 likes · 5 min read

MySQL 8.0.18 adds the EXPLAIN ANALYZE feature, which runs a query and reports actual execution times, row counts, and loop iterations, enabling developers to compare estimated costs with real performance and fine‑tune their queries for better efficiency.
EXPLAIN ANALYZEMySQLPerformance Tuning
0 likes · 8 min read


ITPUBSep 19, 2019 · Databases
MySQL 8.0 introduces Hash Join for dramatically faster large‑dataset queries, supports in‑memory and spill‑to‑disk processing, can replace Block Nested‑Loop joins, and adds EXPLAIN ANALYZE with detailed runtime statistics and tree‑style output, highlighting the platform’s rapid evolution.
Database PerformanceEXPLAIN ANALYZEHash Join
0 likes · 3 min read
