(www.cs.cmu.edu)

366 points virtualwhys | 4 comments | 20 Oct 24 15:30 UTC | HN request time: 0s | source

Show context

fforflo ◴[20 Oct 24 19:57 UTC] No.41898053[source]▶

OrioleDB was supposed to tackle this problem with a new storage engine . https://github.com/orioledb/orioledb

replies(1): >>41898410 #

1. kiwicopple ◴[20 Oct 24 21:00 UTC] No.41898410[source]▶

(I’m on the Supabase team)

Oriole has joined us at supabase now and it’s being worked on full time by Alexander and his team. Here is the patch set:

It will be available to try on the supabase platform later this year too

2. fforflo ◴[20 Oct 24 21:03 UTC] No.41898435[source]▶

Yeah, I've been keeping an eye on the pgsql-hackers discussions. Alexander+team are doing great work.

3. justinclift ◴[20 Oct 24 23:23 UTC] No.41899346[source]▶

As a data point, there are easily noticeable typos on that docs page. Might be a good idea to have someone run a spell checker over it at some point?

4. philippemnoel ◴[21 Oct 24 00:15 UTC] No.41899603[source]▶

The whole ParadeDB team is really excited for OrioleDB and Supabase to ship this :) It's long overdue in the Postgres ecosystem!

MVCC – the part of PostgreSQL we hate the most (2023)