OrioleDB public beta: a Postgres storage engine for update-heavy tables

Supabase has introduced OrioleDB, an open-source Postgres storage engine, as a public beta option for new projects on all plans at standard Postgres pricing, though it is not yet recommended for production. Designed to address limitations of Postgres’s default heap storage, OrioleDB uses undo logs, 64-bit transaction IDs, index-organized tables, lock-free page reads, and copy-on-write checkpoints to reduce table bloat, lessen VACUUM dependence, and improve performance under update-heavy or high-concurrency workloads. Supabase’s public DBArena benchmarks found that OrioleDB delivered the strongest throughput per dollar when datasets exceeded memory capacity, reaching roughly 1.8 times the transactions per minute of standard Supabase Postgres on an 8XL instance, while gains were smaller for memory-resident and read-mostly workloads. It is suited to frequently updated data such as inventory, orders, queues, and sessions, but users are encouraged to benchmark their own workloads, particularly when relying on non-B-tree indexes. The beta can only be selected during new project creation and supports core managed features, but lacks point-in-time recovery and some extensions and commands, cannot coexist with Multigres, and is not yet available for self-hosted Supabase.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.