oriole

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

Cicada <- Mantis <- Oriole <- Courtier <- Pond, of which only the first three are explicit...

If there are other postgres companies that would like to use oriole, feel free to reach out.

That API needs to undergo changes to account for things that Oriole is trying to do.

Neon and Oriole (acquired by Supabase) are both open source and separate storage and compute.

I’m glad to see someone working with oriole, been wanting to do something similar for a long while.

Projects like Oriole have started and sputtered out several times (zheap, for example).

Think of the Oriole extension which bought by Supabase in April 2024.

Tangentially: we have a working prototype for decoupled storage and compute using the Oriole extension (also in the blog post).

Are there plans to build flashback-like functionality on top of Oriole DB?

I'm curious to try out Oriole on our platform when I get some time.

The acquisition of Oriole is very interesting.

How many non-white potential birders have actually complained about bird names such as "Anna's Hummingbird, Gambel's Quail, Lewis's Woodpecker, Bewick's Wren, Bullock's Oriole"?

- Oriole: a postgres extension that's a "drop-in replacement" for the default storage engine We also hope that the team can help develop Pluggable Storage in Postgres with the rest of the community.

Oriole aims to be a drop-in replacement for Postgres' default storage engine and supports similar use-cases with improved performance.

Oriole's design seems to require transaction-aware indexes with point entry removal, which has its own cost.

Oriole are joining to work on the OrioleDB postgres extension.