Time-travel for PostgreSQL: one SELECT vs a full restore vs replaying the WAL
PostgreSQL can now tell you what a row contained at any past moment, with a normal SELECT. One example, against restore and WAL replay.
PostgreSQL can now tell you what a row contained at any past moment, with a normal SELECT. One example, against restore and WAL replay.
Two ways to keep database history. Not a speed contest: what survives a real incident, and what history costs you every day.
Four operations questions about Time Travel SQL: multi-TB tables, retention, monitoring and partitioning.
MySQL was the only major OLTP database without time-travel queries. Here is how that gap closes, with no fork and no ALTER TABLE storm.