v1.3.0

[tjgreen42]

What's Changed

This release includes architectural revisions for compatibility with disaggregated storage architectures (including AWS Aurora, Google Alloy, Neon, and Microsoft HorizonDB). v1.2.0 had introduced custom WAL entries to fix an issue with physical replication keep the memtable on the replica in sync with the primary). These however are not compatible with the stateless WAL redo used in the systems mentioned earlier. v1.3.0 replaces the shared-memory memtable with a paged version plus a shared-memory cache. The release also contains stability and infrastructure fixes.

New Contributors

• @mory91 made their first contribution in fix: reclaim spilled memtable chain pages #389

Full Changelog: v1.2.0...v1.3.0

---

This discussion was created from the release v1.3.0.