HackerTrans
TopNewTrendsCommentsPastAskShowJobs

mebcitto

278 karmajoined 9 tahun yang lalu

Submissions

Open-source cloud-native Postgres platform

github.com
1 points·by mebcitto·15 hari yang lalu·0 comments

Postgres on K8s with fast data branching

github.com
3 points·by mebcitto·2 bulan yang lalu·0 comments

Exposing ZFS volumes over the network via NVMe-oF

xata.io
4 points·by mebcitto·2 bulan yang lalu·0 comments

Xata OSS: Postgres platform with branching, now Apache 2.0

xata.io
1 points·by mebcitto·3 bulan yang lalu·0 comments

Fixing UUIDv7 (for database use-cases)

brooker.co.za
4 points·by mebcitto·9 bulan yang lalu·1 comments

comments

mebcitto
·3 hari yang lalu·discuss
Perhaps pure pgrx extensions would make sense as a first target?
mebcitto
·3 hari yang lalu·discuss
Does it support the extension ecosystem? Or would extensions need to be rewritten as well?
mebcitto
·3 hari yang lalu·discuss
Not sure it’s so simple. I think close to 100% of new ambitious projects are going to leverage AI at least to some degree. I know a couple that have strict no-AI policies (e.g. Zig), but it’s a tiny minority i think.

So how much AI usage does it make it an “AI rewrite”?
mebcitto
·2 bulan yang lalu·discuss
Unfortunately there is currently an issue in pnpm that makes `minimumReleaseAge` difficult: https://github.com/pnpm/pnpm/issues/11068
mebcitto
·2 bulan yang lalu·discuss
That might be opus 4.7 behaviour because I also get that all the time in the past few weeks. Also complex code base, but likely an order of magnitude simpler than yours.
mebcitto
·3 bulan yang lalu·discuss
This rings true to me. Rust is great but in environments where you need a lot of unsafe anyway, it’s still not memory safe, and adds complexity otherwise.
mebcitto
·9 bulan yang lalu·discuss
That explains why `sync` and `worker` have so similar results in almost all runs. The benchmarks from Tomas Vondra (https://vondra.me/posts/tuning-aio-in-postgresql-18/) showed some significant differences.
mebcitto
·9 bulan yang lalu·discuss
Yeah, I don't think "fixing" is really the right term here, since this brings a different set of tradeoffs. You don't leak timestamps, you get ok page locality, but you lose the ability to sort by the IDs. I do see how this might be a good choice for a general PK default (i.e. by default, don't leak stuff).
mebcitto
·9 bulan yang lalu·discuss
It's Postgres specific but there is https://github.com/xataio/pgroll which takes the automation a step further.