Postgres rewritten in Rust, now passing 100% of the Postgres regression tests
1–10 of 756 posts
Re: Postgres rewritten in Rust, now passing 100% of the Postgres regression tests
#2I feel like we need to heavily differentiate between a rewrite and an AI rewrite.
Re: Postgres rewritten in Rust, now passing 100% of the Postgres regression tests
#3I start to see a lot of these re-writes that depend on tests to state that its working. But the things that make software like Postgres and SQLite reliable are not mostly the test, but the real world production scars. That's where the reliability comes from, years and years of running in production.
Re: Postgres rewritten in Rust, now passing 100% of the Postgres regression tests
#4I feel like we need to heavily differentiate between a rewrite and an AI rewrite.
I agree but I think from Bun we learned that a project with really good tests and enough tokens can be converted from one language to another quite good!
Re: Postgres rewritten in Rust, now passing 100% of the Postgres regression tests
#5Woah! AGPL? That's interesting. I think Postgres has shown an open source SQL server didn't need a copy-left license to develop sustainably, so I'm not entirely aure about that, but I do like the license in general.
Re: Postgres rewritten in Rust, now passing 100% of the Postgres regression tests
#6I feel like we need to heavily differentiate between a rewrite and an AI rewrite.
Is there any measurable difference in quality between the two, or are you just going on "vibes"? Is there a correlation between the quality of the manually written code and AI generated code driven by the same dev?
Such crude takes only cause unnecessary friction. If you have a black box that spits out code, and you are unable to distinguish the quality between a top tier dev and an AI inside the black box, then the distinction is unnecessary. Most of the code on the internet is already a black box to you. What percentage of code running on your machines have you vetted by who wrote it and code quality?
AI coding isn't going anywhere and will likely end up generating most code going forward so instead of rejecting it outright or arbitrarily categorizing it we need to focus on solid quantitative and qualitative measures of code and functionality regardless of who wrote it.
Re: Postgres rewritten in Rust, now passing 100% of the Postgres regression tests
#7I start to see a lot of these re-writes that depend on tests to state that its working. But the things that make software like Postgres and SQLite reliable are not mostly the test, but the real world production scars. That's where the reliability comes from, years and years of running in production.
In a project like PostgreSQL, those scars are reflected in unit tests demonstrating that they’re fixed. It’d be hard to pass its test suite and not be as robust as the original.
Re: Postgres rewritten in Rust, now passing 100% of the Postgres regression tests
#8We had one for SQLite (which is SQL-ite btw, not SQ-Lite which doesn't make any sense) via Turso, no wonder we see the same for Postgres. Personally I do want to see libraries be in as much memory safe languages as possible.
Re: Postgres rewritten in Rust, now passing 100% of the Postgres regression tests
#9I feel like we need to heavily differentiate between a rewrite and an AI rewrite.
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”?
Re: Postgres rewritten in Rust, now passing 100% of the Postgres regression tests
#10I start to see a lot of these re-writes that depend on tests to state that its working. But the things that make software like Postgres and SQLite reliable are not mostly the test, but the real world production scars. That's where the reliability comes from, years and years of running in production.
And also the amount of people running it in thousands of scenarios. Not sure if these areas can be even tested for, but I guess time will tell (can observe Bun if it breaks somewhere as that’s afaik the first big AI rewrite which got into prod for masses).