This article explains how MySQL redo logs and binlog logs work together to ensure data durability, consistency, and high availability, covering InnoDB crash‑recovery, flush policies, log file groups, binlog formats, two‑phase commit, and the complete recovery workflow.
This article introduces MySQL’s three primary logs—redo log, binlog, and undo log—explaining their purposes, how they ensure durability and recovery, the mechanisms for flushing them to disk, and the key differences among them, along with practical configuration recommendations.
This article explains the purpose and mechanics of MySQL's binlog, redo log, and undo log, covering their structures, use cases such as replication and recovery, flush timing parameters, format options, and how they together ensure data durability and consistency in InnoDB.
This article explains MySQL's layered architecture, the roles and mechanisms of redo log and binlog, their write and flush strategies, crash‑safe guarantees, and how two‑phase commit ensures consistency, providing practical commands and configuration tips for reliable database operation.
This article explains MySQL's two essential logs—redo log and binlog—by describing the database's layered architecture, the write‑ahead logging mechanism, persistence strategies, crash‑safe guarantees, and how a two‑phase commit ensures consistency between them.
This article explains MySQL’s essential logging mechanisms—binary log, redo log, and undo log—detailing their structures, purposes, configuration parameters, and how they work together to support replication, crash recovery, and transaction durability while balancing performance and consistency.
This article explains how DBAs can use PostgreSQL's extensive logging parameters and log_line_prefix settings to locate and reconstruct every SQL statement within a transaction, illustrated with practical cases, command‑line examples, and step‑by‑step log‑analysis techniques for lock troubleshooting.
This article explains the three essential log files involved in MySQL write operations—redo log, binary log, and undo log—detailing the two‑phase commit process, their roles, write timing, storage mechanisms, and how they enable data durability, recovery, and replication.
This article explains MySQL’s essential logging mechanisms—binary log, redo log, and undo log—covering their purposes, formats, flushing strategies, usage in replication and recovery, and how they interact to ensure data durability and consistency.
This article explains the distinct purposes of MySQL's InnoDB redo log and server‑level binlog, how they work together during large update operations, the concepts of write position, checkpoint, and two‑phase commit, and why both logs are essential for durability and replication.
This article explains MySQL’s essential logging mechanisms—binlog, redo log, and undo log—covering their purposes, formats, configuration parameters, flushing strategies, and roles in replication, recovery, and transaction atomicity, while comparing their differences and illustrating concepts with diagrams.
This article explains the purpose, structure, and usage scenarios of MySQL's binlog, redo log, and undo log, detailing how they support replication, crash recovery, and transaction atomicity while balancing performance and data safety.
This article explains the three most important MySQL log types—redo log, undo log, and binary log—detailing their purposes, contents, creation and release timing, related configuration parameters, physical files, and how they interact with transaction processing and replication.
This article explains the purpose, content, generation timing, storage files, and release mechanisms of MySQL's redo log, undo log, and binary log, highlighting their roles in transaction durability, MVCC, and replication, and clarifying key differences and interactions among them.
This guide explains why a numeric column turned null, compares using the volatile v$sql view with a permanent logging solution, and details step‑by‑step how to create a tablespace, logging table, stored procedure, and scheduled job to capture all Oracle SQL statements.
