3 ms·
OrioleDB was supposed to tackle this problem with a new storage engine . https://github.com/orioledb/orioledb https://github.com/orioledb/orioledb
by fforflo 2y ago
OrioleDB was supposed to tackle this problem with a new storage engine . https://github.com/orioledb/orioledb https://github.com/orioledb/orioledb
- kiwicopple 2y ago(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: https://www.orioledb.com/docs#patch-set https://www.orioledb.com/docs#patch-set It will be available to try on the supabase platform later this year too
- fforflo 2y agoYeah, I've been keeping an eye on the pgsql-hackers discussions. Alexander+team are doing great work.
- justinclift 2y agoAs 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?
- philippemnoel 2y agoThe whole ParadeDB team is really excited for OrioleDB and Supabase to ship this :) It's long overdue in the Postgres ecosystem!