What does HackerNews think of orioledb?

OrioleDB – building a modern cloud-native storage engine (... and solving some PostgreSQL wicked problems) Β πŸ‡ΊπŸ‡¦

Language: C

#6 in Database
#8 in PostgreSQL
#10 in PostgreSQL
#10 in SQL
There are some interesting things in development to potentially solve that problem.

Here's a recent HN submission about OrioleDB of the more promising ones: https://news.ycombinator.com/item?id=36740921

Source code: https://github.com/orioledb/orioledb

I'm excited about the title, but I have to say that my initial impression has left me frustrated. The main README on GitHub[1] smells of corporate-speak. So far I've learned that:

- OrioleDB is a new storage engine for PostgreSQL

- PostgreSQL is most-loved (whatever that means)

- OrioleDB is an extension that builds on.. other extensions?

- OrioleDB opens the door to the cloud!

In the wake of crypto and other Web 3.0 grift, this is not the tact that I'd take to release something that extends and improves on something as important as PostgreSQL.

[1] https://github.com/orioledb/orioledb

OT & Apologies for being unspecific, but can anyone else jog my memory about the open source fork 2-3 years ago that was going to try to pretty heavily edit internals/try some of new architectural designs? Some searches have not lead me back to the name of it...

Edit: OrioleDB! https://github.com/orioledb/orioledb https://news.ycombinator.com/item?id=30462695

The 2021 slidedeck on problems & possibilities in postgres was super fun to read! Solving postgresql's wicked problems. https://www.slideshare.net/AlexanderKorotkov/solving-postgre...

One of the more exciting projects in this space is OrioleDB[0] (disclosure: supabase is an investor/sponsor).

In Postgres 14 their patchset was ~5,000 lines of code (representing the total number of changes required in their fork). In the upcoming Postgres 16 release, it is ~2,000 lines of code. That means that around 60% of the code is already committed to the Postgres core.

We're hopeful that these changes can provide the possibility of several new storage implementations for postgres, much like the MySQL ecosystem have with their pluggable storage

[0] https://github.com/orioledb/orioledb

I took a look at https://github.com/orioledb/orioledb which is a project attempting to remedy some of Postgres' shortcomings, including MVCC. It looks like they're doing something similar to MySQL with a redo log, as well as some other optimizations. So maybe this is the answer.
I think there is a new project from the Postgres community. They try to replace the storage engine to solve the inefficiency caused by MVCC

https://github.com/orioledb/orioledb

> I wonder how they make transactional workloads 2x faster vs normal Postgres

There can be improvements like what OrioleDB is trying to do: https://github.com/orioledb/orioledb/

> I’d love to see B-Tree primary storage option. Aka store the row data inside the primary index.

It is coming: https://github.com/orioledb/orioledb

A couple of months back there was a post from someone who made a presentation about a lot of things that are 'bad' in postgres (mostly performance-wise) and a github repo that tried to fix that (in first instance with patches and the idea was to later have it either upstreamed or as an addon).

I can't find anything of this effort anymore. Does someone know what I'm talking about and what the current status of that is?

EDIT: found it: https://github.com/orioledb/orioledb

I'd love to hear what PG devs here think of his criticism and proposed solutions.

OrioleDB seems like a more complete distributed postgres (https://github.com/orioledb/orioledb). It uses RAFT as well as a bunch of other changes too