3 ms·
Thanks for verifying the benchmarks. We’re close to a full RC, aiming for December Just to add: if anyone wants to contribute (beyond code) benchmarking and st
by kiwicopple 1y ago
Thanks for verifying the benchmarks. We’re close to a full RC, aiming for December
Just to add: if anyone wants to contribute (beyond code) benchmarking and stress-testing is very helpful for us
- Sesse__ 1y agoI assume you get this a lot, but how much patching is left in PG 18?
- kiwicopple 1y agoWe are tracking the patches here: https://www.orioledb.com/docs#patch-set https://www.orioledb.com/docs#patch-set The actual storage engine is written as an extension - these patches are mostly to improve the TAM API. If these are accepted by the community then it should be simpler for anyone to write their own Storage extensions. I think (correctly) it will take a lot longer to upstream the extension - the PG community should take a “default no” attitude with big changes like this. Over time we will prove its worthiness (hopefully beyond just supabase - it would be good to collaborate with other Postgres providers)
- Sesse__ 1y agoOK, so basically no big change with PG 18, and for the time being, one needs to basically your own Postgres? Would be really nice with a pgdg package, as this is definitely the kind of thing I would want to test in a separate cluster :-)