This article compares PostgreSQL and MySQL across complex query optimization, data types, MVCC implementation, transaction rollback capabilities, and cloud ecosystem support, explaining why PostgreSQL is increasingly preferred for complex analytics, vector search, and geospatial applications.
This article explains the complete InnoDB undo‑log rollback process on MySQL 8.0, covering preparation, reading and parsing undo logs, constructing primary‑key index records, and the detailed steps for deleting secondary and primary index entries during a transaction rollback.
This article explains how MySQL 8.0.32 (InnoDB) handles a situation where the client sends a DML/DDL statement, the server executes it, and the client silently drops the connection before the server can detect the disconnect, detailing transaction commit, rollback, and send() behavior.
This article explains how pressing Ctrl+C in the MySQL client triggers a KILL QUERY command, details the server's multi‑step handling—including thread coordination, flag setting, and transaction rollback—and clarifies differences when autocommit is on or off.
This article evaluates two techniques for accelerating rollback of large MySQL transactions—dynamically enlarging the InnoDB buffer pool and using innodb_force_recovery=3 with instance shutdown—by presenting experimental steps, code examples, performance measurements, and practical recommendations.
When writing integration tests that involve database operations, developers must ensure that test execution does not pollute the original data, and the article explores strategies such as using transaction rollbacks, recreating databases, and mocking database interfaces to maintain data integrity.
