Databricks

What if an agent could branch, rewind, or query a past Postgres state without copying the database first? Lakebase Postgres makes transaction history addressable by treating the WAL as the source of truth and decoupling compute from storage. That means: • Branch from a specific LSN with copy-on-write • Restore to an earlier LSN without copying data back • Query past database states directly within the history window For agentic workloads, that makes isolated, reversible database workflows much lighter weight. https://t.co/07yQo2VB7g