[dkhenry]

OrioleDB isn't a separation of storage and compute, its a more efficient storage engine for Postgres to replace the existing HEAP engine. This is like how in MySQL we could swap MyISAM for InnoDB and eventually RocksDB.

I did some benchmarks on it previously to show how much of an improvement it gives over the stock HEAP engine

EDIT: correct link to the public dashboard below, thanks for the heads up @kiwicopple

https://airtable.com/app7jp5t0dEHyDpa8/shr00etqywoDW2N6N

[CathalMullan]

There's an experimental feature which separates storage and compute.

https://www.orioledb.com/docs/usage/decoupled-storage

[iamdanieljohns]

Is the need for Oriole negated by using a system that separates storage from compute like Neon, Xata?

[nikita]

(Neon CEO)

Not really. OrioleDB solve the vacuum problem with the introduction of the undo log. Neon gives you scale out storage which is in a way orthogonal to OrielDB. With some work you can run OrioleDB AND neon storage and get benefits of both.

[akorotkov]

> OrioleDB solve the vacuum problem with the introduction of the undo log.

Way more than just this!

> With some work you can run OrioleDB AND neon storage and get benefits of both.

This would require significant design work, given that significant OrioleDB benefits are derived from row-level WAL.

[tudorg]

Answering on behalf of Xata, it is orthogonal. I'm curious to try out Oriole on our platform when I get some time.

[kiwicopple]

fwiw I couldn't access your airtable link, but I found this one online:

https://airtable.com/app7jp5t0dEHyDpa8/shr00etqywoDW2N6N

thanks for running the benchmarks, it helps to have external parties verifying the progress