Tagged articles
WAL
47 articles · Page 1 of 1
A step-by-step guide for DBAs to handle database disk space emergencies in the final 10 minutes, covering confirmation, growth identification, safe buffering, write throttling, online expansion, and verification for PostgreSQL and MySQL, emphasizing evidence-driven actions over risky shortcuts.
MySQLOperationsPostgreSQL
0 likes · 46 min read

This article systematically breaks down database high availability into five layers — single-node durability via WAL and two-phase commit, master-slave replication with async and semi-sync modes, GTID-based global transaction identification, consistent failover with fencing, and automated failover using Orchestrator and probe-agent — illustrating each with real-world failure cases and configuration details.
Crash RecoveryFailoverGTID
0 likes · 25 min read

This article details a five-layer database high availability architecture: single-node crash recovery via WAL and two-phase commit, asynchronous and semi-synchronous replication trade-offs, GTID-based global transaction identification for seamless failover, fencing mechanisms to prevent split-brain, and Orchestrator with probe-agent for automated failure detection and failover execution.
Crash RecoveryFailoverFencing
0 likes · 26 min read

This article systematically explains database high availability through five layers: single-node crash recovery via WAL and two-phase commit, replication modes (async vs semi-sync) and RPO trade-offs, GTID-based global transaction identification for safe failover, fencing and PRS/ERS switching protocols to prevent split-brain, and Orchestrator's cross-check failure detection with probe-agent for automated failover.
Crash RecoveryFailoverGTID
0 likes · 28 min read

WeChat uses SQLite for chat storage because its embedded, zero-process design fits mobile constraints; ACID transactions and B+tree indexes ensure message durability and fast pagination; WAL enables concurrent reads/writes; SQLCipher encrypts per-device; sharding by session mitigates single-writer limits, offering a blueprint for local-first apps.
ACIDB+TreeMobile Database
0 likes · 5 min read

This article analyzes why rolling back a Milvus 3.0 upgrade is far riskier than the upgrade itself, explaining how Storage V3, index version changes, WAL message semantics, and SDK/proto contracts create irreversible state boundaries that a simple image tag revert cannot undo.
Loon FFIMilvusSDK compatibility
0 likes · 21 min read

The article breaks down five durability tiers for database writes—from in‑memory acknowledgment to cross‑availability‑zone replication—explaining how the point at which success is reported determines latency, fault tolerance, and the hidden coordination work a system must perform.
Object StorageRaftReplication
0 likes · 14 min read

This article explains how to capture and stream row‑level changes from PostgreSQL using its Write‑Ahead Log, compares the approach with MySQL binlog CDC, and provides a step‑by‑step guide—including configuration, logical decoding, snapshot handling, replication slots, and production‑grade correctness considerations—to build a reliable CDC pipeline.
CDCLogical DecodingPostgreSQL
0 likes · 29 min read

Milvus 3.0 replaces the dual‑track write path of 2.x with a unified WAL‑first design, introduces a three‑layer channel model (PChannel, VChannel, CChannel) and a five‑layer interceptor chain, adds the Woodpecker WAL that outperforms Kafka/Pulsar by up to 5.8×, and provides pluggable back‑ends, atomic broadcasting, and provable recovery mechanisms.
MilvusStreaming ArchitectureWAL
0 likes · 27 min read

This comprehensive guide walks through PostgreSQL's backup and replication architecture, explaining WAL fundamentals, the distinction between backup, high‑availability, disaster‑recovery and CDC, and provides step‑by‑step configurations, performance trade‑offs, monitoring queries, Kubernetes deployment tips, and practical recovery‑drill procedures for production environments.
CDCHAPITR
0 likes · 40 min read

This article dissects PostgreSQL's Write‑Ahead Logging (WAL), explaining how it underpins transaction durability, replication, CDC, point‑in‑time recovery, and commit latency, and provides a step‑by‑step guide to architecture design, parameter tuning, troubleshooting, containerization, backup strategies, and operational checklists for production‑grade deployments.
CDCHigh AvailabilityPerformance Tuning
0 likes · 37 min read

This article demonstrates how to design and implement a miniature yet fully functional industrial intelligent scheduling system in Go, leveraging a workflow engine, priority queue, saga‑based transactions with FSM state management, concurrent station execution, and write‑ahead logging for reliable, real‑time factory automation.
ConcurrencyFSMGo
0 likes · 9 min read

This comprehensive guide explains PostgreSQL's Write-Ahead Logging (WAL) fundamentals, its role in durability, crash recovery, PITR and streaming replication, details the checkpoint mechanism, essential monitoring queries, production‑grade configuration recommendations, backup and recovery procedures, and practical DBA checklists for reliable operations.
PostgreSQLReplicationWAL
0 likes · 7 min read


ITPUBDec 9, 2025 · Databases
This article explains SQLite's PRAGMA commands, compares synchronous modes and WAL settings, distinguishes persistent from session‑level pragmas, and highlights key Linux‑Windows differences, providing practical examples and a step‑by‑step initialization checklist for reliable database operation.
Database PerformanceLinuxPRAGMA
0 likes · 11 min read

This comprehensive guide walks you through troubleshooting PostgreSQL physical (stream) replication, covering environment prerequisites, anti‑pattern warnings, step‑by‑step diagnostics for replication lag, split‑brain scenarios, replication slot problems, monitoring setup with Prometheus, and best‑practice recommendations to keep your primary‑standby cluster healthy.
PostgreSQLReplicationWAL
0 likes · 35 min read

This article walks through building a database storage engine from a simple shell script to a full distributed key‑value system, covering in‑memory indexing, SSTable creation, LSM‑Tree architecture with compaction, replication strategies, and sharding techniques for scaling across multiple machines.
B+TreeData ShardingDistributed Database
0 likes · 38 min read

Explore 15 classic MySQL log interview questions covering redo log, WAL, binlog, undo log, two‑phase commit, write‑ahead logging, crash‑safe mechanisms, log flushing settings, and recovery procedures, with detailed explanations, execution flow diagrams, and configuration parameters to help you ace database engineering interviews.
Two-Phase CommitWALbinlog
0 likes · 16 min read

This article presents 15 classic MySQL log interview questions and provides detailed explanations of redo log, WAL, binlog, undo log, two‑phase commit, log flushing mechanisms, and recovery strategies, helping readers deepen their database knowledge and ace technical interviews.
MySQLWALbinlog
0 likes · 18 min read

An in‑depth guide explains MySQL’s write‑ahead log mechanism, covering buffer pool, redo and undo logs, checkpoint types, and how the system recovers from power failures, with step‑by‑step examples and practical configuration tips for reliable data consistency.
MySQLWALcheckpoint
0 likes · 12 min read


ITPUBMay 6, 2024 · Databases
This article explains MySQL InnoDB’s write‑ahead logging, detailing the roles of Buffer Pool, Redo and Undo logs, checkpoint mechanisms, and how they ensure data consistency and atomicity when a sudden power loss occurs.
InnoDBMySQLWAL
0 likes · 12 min read


政采云技术Dec 27, 2023 · Databases
This article explains MySQL's binary log (binlog), a binary format file that records SQL statements for database updates, its role in master-slave replication, crash recovery, and detailed implementation mechanisms including cache management and event writing processes.
Crash RecoveryDatabase InternalsDatabase Replication
0 likes · 8 min read

This article walks through building a simple yet enterprise‑grade key‑value storage engine in Go, covering WAL implementation, LSM‑Tree structure, SkipList‑based in‑memory storage, transaction handling for Put/Get/Delete, and the on‑disk log format, with a complete 1,000‑line codebase hosted on GitHub.
GoKV storeLSM-tree
0 likes · 6 min read

This article explains MySQL's transaction implementation, covering write‑ahead logging, transaction IDs, multi‑version concurrency control, buffer pool management, and the roles of redo and undo logs in ensuring durability and atomicity.
Buffer PoolMVCCMySQL
0 likes · 27 min read

This article explains SQLite's Rollback and WAL logging modes, compares their performance and concurrency characteristics, investigates a real‑world problem where duplicate IM message IDs appear after app upgrades, and presents a step‑by‑step solution using UNIQUE constraints and index checks to prevent repeated inserts.
Database MigrationIndexSQLite
0 likes · 26 min read

This article examines the drawbacks of using UUIDs as primary keys in PostgreSQL—highlighting WAL and index bloat, performance penalties, benchmark comparisons with sequences, and suggests ordered UUID alternatives for better scalability and maintainability.
Index BloatPostgreSQLSequential UUID
0 likes · 9 min read

This article explores MySQL’s write‑ahead log, two‑phase commit, engine plugins, memory management, lock strategies, and state‑machine design, showing how these internal mechanisms can inspire more reliable, scalable, and maintainable business system architectures.
Database ArchitectureMySQLTwo-Phase Commit
0 likes · 22 min read

This article examines SQLite's journal modes, Android's thread and connection‑pool configurations, and demonstrates through source‑code analysis that converting a database from the default rollback‑journal mode to write‑ahead logging (WAL) is safe and improves concurrency performance.
AndroidDatabase PerformanceJournal Mode
0 likes · 16 min read


ITPUBFeb 28, 2022 · Databases
This article explains how a deep understanding of database internals, illustrated by an Oracle recovery story, enables you to restore PostgreSQL instances when WAL files or pg_control are missing, providing detailed command parameters, preparation steps, and cautions for safe recovery.
OraclePostgreSQLWAL
0 likes · 10 min read

This article explains why PostgreSQL data loss occurs, compares DDL and DML causes, and reviews several recovery tools—including pg_resetwal, pg_dirtyread, pg_recovery, pg_filedump, WalMiner, and pageinspect—providing usage examples, summaries, and practical recommendations for effective data restoration.
Database ToolsMVCCPostgreSQL
0 likes · 14 min read

This guide walks through setting up PostgreSQL's Point‑In‑Time Recovery (PITR) by enabling WAL archiving, performing a base backup, simulating data loss, and restoring the database to a specific timestamp, complete with command‑line examples and verification steps.
PITRPostgreSQLRecovery
0 likes · 9 min read

This article explains common database logging mechanisms such as MySQL redo logs and binlogs, compares them with Redis AOF and etcd's Raft‑based WAL, and provides an in‑depth analysis of etcd's WAL source code, including key structures, creation process, record types, encoding, and file pipeline management.
Database LogsGoRaft
0 likes · 18 min read

This article explains how PolarDB ensures transaction atomicity by analyzing ACID principles, detailing the shortcomings of simple Direct‑IO and Buffer‑IO, introducing write‑ahead logging, full‑page backup, checkpointing, visibility mechanisms, and distinguishing durability and atomicity points to achieve reliable crash recovery and consistent data visibility.
Crash RecoveryPolarDBWAL
0 likes · 30 min read

This article explains how PolarDB implements transaction atomicity by combining write‑ahead logging, buffer management, full‑page backup, CLOG, and ProcArray mechanisms to ensure crash‑safe recovery, consistent visibility, and durable commits within the database system.
PolarDBWALdatabase
0 likes · 31 min read

This article explains the essential role of logging and recovery mechanisms—especially the ARIES algorithm—in ensuring ACID properties, covering physical vs logical logging, optimization techniques like group commit and early lock release, and the three-phase recovery process.
AriesLoggingRecovery
0 likes · 19 min read

This article explains why a low‑traffic PostgreSQL 11 database can accumulate massive WAL files, analyzes relevant configuration parameters and replication slots, demonstrates diagnostic SQL commands, and provides step‑by‑step actions—including adjusting archive_timeout, handling replication slots, and forcing a checkpoint—to reclaim disk space.
Performance TuningPostgreSQLWAL
0 likes · 8 min read

The article explains how Write Ahead Log (WAL) improves metadata persistence and disaster recovery in distributed storage systems such as HDFS by buffering changes, reducing synchronous database writes, and providing checkpoint and recovery mechanisms, while also discussing practical control options.
HDFSMetadata PersistenceWAL
0 likes · 5 min read

MySQL achieves crash‑safe durability by employing a write‑ahead log architecture that records changes in redo, undo, and binary logs, coordinates them through two‑phase and group commit to maintain order, and uses a structured recovery process to replay or roll back transactions after any failure.
Crash SafetyGroup CommitMySQL
0 likes · 17 min read

This article explains InfluxDB's storage engine workflow—including WAL, Cache, TSM files, compression components, and file management—then provides hardware sizing guidance based on write/query load, series cardinality, and recommends SSD storage with sample configuration settings.
InfluxDBTSMWAL
0 likes · 5 min read

This article explains how to handle high‑concurrency instant‑messaging scenarios by designing message deduplication, optimizing SQLite write performance with batch inserts and WAL mode, improving query speed with indexes and caching, and reducing UI refresh overhead through delayed and scroll‑aware updates.
SQLiteWALinstant messaging
0 likes · 19 min read


ITPUBOct 24, 2019 · Databases
This article explains the design and implementation of JDTX, a distributed transaction middleware that combines MVCC, WAL, and a one‑phase commit model to provide strong ACID guarantees, high performance, and multi‑database support while outlining its challenges and future roadmap.
Database MiddlewareJDTXMVCC
0 likes · 17 min read

This article introduces JDTX, a high‑performance, ACID‑compliant distributed transaction middleware, explains its architecture based on WAL and MVCC, compares rigid two‑phase commit and flexible BASE‑based approaches, and discusses the technical difficulties and future roadmap for integrating JDTX with Apache ShardingSphere and cloud‑native platforms.
ACIDDatabase MiddlewareJDTX
0 likes · 15 min read

This article explains MySQL's binlog group commit mechanism, detailing the three stages—Flush, Sync, and Commit—how they interact with redo logs and crash‑safe parameters, and analyzes a known bug in the Sync stage that was fixed in later MySQL versions.
MySQLWALredo log
0 likes · 7 min read

An in‑depth look at SQLite’s Write‑Ahead Logging (WAL) mode and the asynchronous checkpoint optimization used in WeChat’s WCDB, covering implementation details, performance gains, A/B test results, and practical code examples for enabling these features on Android.
Asynchronous CheckpointSQLiteWAL
0 likes · 13 min read

This article examines the evolution of write-ahead logging in relational databases, compares MySQL and PostgreSQL implementations, highlights the scalability limits of centralized WAL designs, and explores how distributed logging with global timestamps, dependency tracking, and hole‑avoidance techniques could dramatically improve single‑node database throughput.
MySQLPostgreSQLWAL
0 likes · 16 min read

The article explains HBase’s write‑ahead‑log architecture, detailing how client put/delete requests travel through RPC to the RegionServer, are processed by MultiRowMutationService, written to the WAL via FSHLog.append and sync, and finally stored in MemStore, while describing durability options and the underlying source‑code call chain.
HBaseJavaWAL
0 likes · 10 min read

This talk details how Tencent's iOS engineers tackled SQLite performance bottlenecks by redesigning multithreaded concurrency, optimizing Busy Retry handling, leveraging WAL and mmap, and applying low‑level I/O and lock improvements, resulting in dramatic reductions in UI lag and CPU waste for heavy‑use users.
MultithreadingSQLiteWAL
0 likes · 17 min read


ITPUBJun 15, 2016 · Databases
This article explains HBase’s internal architecture, covering the roles of HRegionServer, Client, Zookeeper, Master, RegionServer, the physical storage layout, StoreFile and HFile structures, and the Write-Ahead Log mechanism that ensures data durability and fault tolerance.
HBaseHDFSNoSQL
0 likes · 13 min read
