Hi Tony, > Personally believe that the Double Write is very smart for MySQL InnoDB, > but not a good ideal for Postgres, currently, WAL is the best solution > for Postgres, > maybe the next generation log system for Postgres could use OrioleDB's > storage engine.
Just to clarify from a technical perspective, both MySQL and PostgreSQL use Write-Ahead Logging (WAL) as their fundamental transaction logging mechanism, so there is no difference in that regard. The comparison here is specifically between Full-Page Writes (FPW) and the Double Write Buffer (DWB). Neither of these concepts conflicts with or replaces the core WAL design. Instead, both are simply different techniques implemented to solve the exact same issue: preventing torn pages during a crash. My proposal is aimed at discussing the performance tradeoffs and implementation details between these two specific torn-page protection mechanisms, rather than replacing WAL itself. Regards, Baotiao
