Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Postgres rewritten in Rust, now passing 100% of the Postgres regression tests

github.com

Post reply on HN
Print view View original

501–510 of 756 posts

Re: Postgres rewritten in Rust, now passing 100% of the Postgres regression tests

#501

Post by andai »

Blahagun wrote: post #483
sdevonoes wrote: post #251

Don’t understand these rewrites. - typically they are behind a single person. That’s usually bad because of spf - typically they are achieved in a very short amount of time, so the author hasn’t acquired any discipline in creating the project. That means it’s unlikely the author is going to stick to the project in the mid and long term - anyone that wants to contribute to the project needs to pay. Needs to pay tokens…

It's a very interesting phenomenon in recent years and most of the discussions about "why" are immediately blocked by the "memory safety" argument, as if it's a silver bullet for all things that are considered "bad" in software implementations. No matter how good the language is, and I consider Rust a very good language, it's practically impossible to replace years of experience and tested code, most of it contribute…

I think we're a year or two away from the same argument being used by languages which enforce proof of correctness. The economics seem to be shifting in that direction.

Finding exploits is getting exponentially cheaper, and the cost of producing proofs is rapidly going down. For a lot of software correctness is rapidly becoming non-optional.

Re: Postgres rewritten in Rust, now passing 100% of the Postgres regression tests

#502

Post by guenthert »

jeltz wrote: post #276
joshka wrote: post #67

Earlier quoted context omitted.

It would be reasonably easy to audit and automate this...

It is not a requirement the PostgreSQL project wants to have. It would be a heavy burden and mostly pointless.

I think it's rather unfortunate that writing regression tests is seen as a heavy burden. Compared to determining the cause of a bug and the right strategy to fixing it in a maintainable way, writing such a test should be simple, no?

I'm not at ease regarding LLM generated code changes to a project with a (hopefully) long expected life time, but LLM generated regression tests should be less contentious. I wouldn't expect them to be maintained much; rather, if they don't perform as intended against a future build, just have them recreated.

Re: Postgres rewritten in Rust, now passing 100% of the Postgres regression tests

#503

Post by andai »

booksock wrote: post #245
dirkc wrote: post #78

How would one go about reviewing a piece of code like this? One of the things I'd typically do is peek at the commit history. Seeing what people worked on and how they did it tends to say a lot about a project. But with LLMs generating 7101 commits in less than a month that isn't feasible. Even looking at a single day is way too much [1]. It probably also doesn't make sense since the commits content won't tell you mu…

(I'm working with malisper on pgrust), I think the focus for projects like this is going to shift to reviewing the testing/fuzzing process instead of reviewing each commit (going much further than what the postgres regression/isolation/crash tests do). related post from danluu: https://danluu.com/ai-coding/

Oh, I just posted a similar comment elsewhere in the thread.

https://news.ycombinator.com/item?id=48856535

Though beyond testing, I think there will be increasing focus on proofs of correctness. (Testing can only show the presence of bugs, not the absence. —Dijkstra)

At any rate, it's never been this cheap to produce the proof of correctness of a program, or on the other hand, to produce an exploit for an incorrect program.

Re: Postgres rewritten in Rust, now passing 100% of the Postgres regression tests

#504

Post by Jean-Papoulos »

sdevonoes wrote: post #251

Don’t understand these rewrites. - typically they are behind a single person. That’s usually bad because of spf - typically they are achieved in a very short amount of time, so the author hasn’t acquired any discipline in creating the project. That means it’s unlikely the author is going to stick to the project in the mid and long term - anyone that wants to contribute to the project needs to pay. Needs to pay tokens…

It's useful to show the actual team that it's possible. From there, they can make the decision of whether to go the bun route with more information.

Re: Postgres rewritten in Rust, now passing 100% of the Postgres regression tests

#507

Post by ur-whale »

processunknown wrote: post #360
____tom____ wrote: post #356

Earlier quoted context omitted.

Yeah. I'm gonna have an LLM rewrite Star Wars and then film it. Should be fine, right?

LGTM. copyright laws don't matter anymore.

> LGTM. copyright laws don't matter anymore.

hear hear, and good riddance too.

Re: Postgres rewritten in Rust, now passing 100% of the Postgres regression tests

#508

Post by menaerus »

rozhok wrote: post #475
booksock wrote: post #244

Earlier quoted context omitted.

(I'm working with malisper on this), we are now focusing on improving many things about postgres! Some we have written about before [0], and we have much more in mind too. Malis wrote another comment about analytical workloads being 300x faster now than postgres for a version we're working on right now Aiming for postgres compatible database with a 2026 architecture [0] https://malisper.me/the-four-horsemen-behind-th…

Wondering if its possible to backport performance improvements into upstream. Should be a big deal.

I'd say it would be most likely impossible.

Re: Postgres rewritten in Rust, now passing 100% of the Postgres regression tests

#509

Post by sevg »

mulmen wrote: post #434
Verdex wrote: post #410

Earlier quoted context omitted.

My first web search (data blades) turned up harbor freight woodworking tools. Then I made a second web search: data blades database. That turned up some ibm database software module technology which I assume is what's being discussed.

I performed both searches on Kagi and didn't see anything about IBM. I do see results for "DataBlade" and "Data blade database" but I didn't try those specific variations after my first two attempts returned nothing of interest. That's too much effort to decipher a HN post.

> That's too much effort to decipher a HN post.

It would have been less effort than it took you to write this comment. Perhaps next time that you can’t be bothered, just ignore the comment and move on to another thread that meets your required spoonfeeding levels.

Post reply on HN