Little known fact is that POSTGRES used to have built-in Time Travel [1]. It was deprecated as the performance hurdle was significant. This seems to utilize l

Little known fact is that POSTGRES used to have built-in Time Travel [1]. It was deprecated as the performance hurdle was significant. This seems to utilize logical WAL replication and some form of dependency generation based on proxying a transaction's reads. Managed Neon (Acquired by Databricks) also offers time travel [2]. One of the biggest challenges with this kind of solutions is handling ACID, OCC and/or HW failures correctly, Sometimes it requires an whole new language! [3] [1] https://www.postgresql.org/docs/6.3/c0503.htm https://www.postgresql.org/docs/6.3/c0503.htm [2] https://neon.com/docs/postgres/backup-restore/time-travel-assist https://neon.com/docs/postgres/backup-restore/time-travel-as... [3] https://apple.github.io/foundationdb/flow.html https://apple.github.io/foundationdb/flow.html