• Sources: primary
  • Summary: OrioleDB plugs into Postgres 17.11 through the Table Access Method. It uses an undo log, 64-bit transaction IDs, index-organized tables and copy-on-write checkpoints. On Supabase's TPC-C-derived DBArena benchmark, it ran about 1.8x the throughput of heap storage on an 8XL instance when data exceeded memory, and heap was faster at Small when data fit in memory. Supabase says the beta is not for production: it has no point-in-time recovery, can only be chosen at project creation, and does not support VACUUM FULL or CLUSTER.
  • Why it matters: Teams that fight autovacuum on update-heavy Postgres tables can test a drop-in alternative engine with a public benchmark method.