Nov 1, 2026 · 20 min · 9 segments
In this episode of Scaling Postgres, we discuss the public beta of Oriole DB, 100,000 times faster queries with GPUs, post pg\_restore to-do and a lesson in data integrity. To get the show notes as…
Creston JamisonHost
Our first piece of content is OrielDB Public Beta, a Postgres storage engine for update-heavy tables.

So the OrielDB team did join Supabase, and now they are moving OrielDB into a public beta.

Now they say it is an open source storage engine for Postgres and it's available on your Supabase plan.

It's moving from storing dead rows, dead tuples in the heap into storing them in an undo log.

And this should have an advantage for update heavy workloads because every update doesn't create a new row.

Yes, it enters something in the undo log, but as long as you don't do a rollback, it would be much faster just to update in place.

So yes, they are using an undo log instead of dealing with the leftover dead tuples in the heap.

What that means is that normally you have the heap and then the indexes are a separate structure, whereas in AurelDB, quote, rows are stored inside the primary key index rather than a separate heap.

Also, there's no buffer mapping, so in-memory pages link directly to their storage pages, and as a result, they say page reads are lock-free.

And they're also using copy-on-write checkpoints and row-level wall, which means they can just write the data that's changed and can, quote, reduce disk IO and write heavy workloads.

Now, this particular beta is on Postgres 17.11, so it does not support the 18 series yet.

Now, I did mention I'm excited about this because these are all very interesting, but I'm a little bit saddened by it.

The reason is because for the longest time it would be great to have a separate storage engine in Postgres that handles update-heavy workloads, or better handles update-heavy workloads.

Because I keep talking about articles in Scaling Postgres, if someone has a queue system that gets a lot of updates, and inevitably it runs into problems.

Our first piece of content is OrielDB Public Beta, a Postgres storage engine for update-heavy tables.

So the OrielDB team did join Supabase, and now they are moving OrielDB into a public beta.

Now they say it is an open source storage engine for Postgres and it's available on your Supabase plan.

It's moving from storing dead rows, dead tuples in the heap into storing them in an undo log.

And this should have an advantage for update heavy workloads because every update doesn't create a new row.

Yes, it enters something in the undo log, but as long as you don't do a rollback, it would be much faster just to update in place.

So yes, they are using an undo log instead of dealing with the leftover dead tuples in the heap.

What that means is that normally you have the heap and then the indexes are a separate structure, whereas in AurelDB, quote, rows are stored inside the primary key index rather than a separate heap.

Also, there's no buffer mapping, so in-memory pages link directly to their storage pages, and as a result, they say page reads are lock-free.

And they're also using copy-on-write checkpoints and row-level wall, which means they can just write the data that's changed and can, quote, reduce disk IO and write heavy workloads.

Now, this particular beta is on Postgres 17.11, so it does not support the 18 series yet.

Now, I did mention I'm excited about this because these are all very interesting, but I'm a little bit saddened by it.

The reason is because for the longest time it would be great to have a separate storage engine in Postgres that handles update-heavy workloads, or better handles update-heavy workloads.

Because I keep talking about articles in Scaling Postgres, if someone has a queue system that gets a lot of updates, and inevitably it runs into problems.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.