Live data from Hacker News

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

github.com

141–150 of 756 posts

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

#141

Earlier quoted context omitted.

> significant part of the rust community consists of software talibans I seriously don't get it though. Rust is a nice language, but so is X. However we don't see X people brigading existing projects with constant bombardment with "rewritten in X". What is that about Rust that prompts this behavior?

It's pretty ergonomic to agents. Like typescript.

[deleted]

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

#143
post #33

Why should a developer use this for anything beyond a pet project? Just because it is written in Rust? All these "rewritten in rust" projects only reinforce the idea that a significant part of the rust community consists of software talibans and not of engineers who must deliver something that works and is reliable over time.

> significant part of the rust community consists of software talibans I seriously don't get it though. Rust is a nice language, but so is X. However we don't see X people brigading existing projects with constant bombardment with "rewritten in X". What is that about Rust that prompts this behavior?

Rust attracts zealots because of the various kinds of safety guarantees. The speed means it can replace more or less anything.

People see the safety as a moral superiority so it attracts obnoxious zealots.

Other languages' features and syntax aren't nearly so easy for zealots to form behind. The perception of absolute safety it puts in some people makes them crazy.

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

#144
I think the cool thing about these projects is that even if test parity reaches 100%, some bugs are going to surface on the new project that don't exist on the original project.

This is usually a good example of a test case that the upstream project is not covering and can be contributed back.

Parity should be bidirectional, so definitely it is possible for both parties to benefit from it.

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

#146

Why so much negativity? I find these projects interesting for learning purposes and exploring new ways. What’s wrong with that?

can you enlighten me, what exactly do you learn from asking a llm to do a rewrite?

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

#147
Hey author here. Wasn't expecting to see this up.

To concisely give an overview of the project, I've been experimenting with using LLMs to build a better version of Postgres. Postgres is 30 years old and we've learned a lot about databases since hten. A lot of the techniques that work for doing a rewrite are also useful for doing a rearchitecture.

I'm now working on a new, not yet published version of pgrust that incorporates a lot of techniques. Currently the new version:

  - Passes 100% of Postgres regression suite
  - Implements a thread per connection model instead of the process per connection model Postgres does
  - Is 50% faster than Postgres on transaction workloads
  - Is ~300x faster than Postgres on analytical workloads. Right now it's 2x slower than Clickhouse on clickbench and I think it's possible to get faster than Clickhouse
If you have any questions, I'm happy to answer them.

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

#149
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…

The github cli has a command to query commits with a sorting asc/desc flag https://cli.github.com/manual/gh_search_commits here's the docs with more syntax using the "before x date" https://docs.github.com/en/search-github/searching-on-github... there's also an advanced search page, but it does not support commits when filtering with dates https://github.com/search/advanced or you can bisect the date in the search wi…

Thanks for all the info you've provided!

Maybe I'm just being a little grumpy. If I really need to look into a repository, I clone it and use vanilla git command line tools to have a look.

It's just annoying that the modern web UI from GitHub takes >1s second to load a page with 34 commits

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

#150

Earlier quoted context omitted.

> significant part of the rust community consists of software talibans I seriously don't get it though. Rust is a nice language, but so is X. However we don't see X people brigading existing projects with constant bombardment with "rewritten in X". What is that about Rust that prompts this behavior?

Rust attracts zealots because of the various kinds of safety guarantees. The speed means it can replace more or less anything. People see the safety as a moral superiority so it attracts obnoxious zealots. Other languages' features and syntax aren't nearly so easy for zealots to form behind. The perception of absolute safety it puts in some people makes them crazy.

This is a good point, actually. Might well be the reason.
Post reply on HN