Introducing pgrust 0.4 beta. 0.4 includes:
@mmalisper1.3K followers
16,538 views
46 Comments
Comments from the original post on X (Twitter)

@VictoriqueM
@pgrustdb "our" this thing is littered with claude code comments.
12 likes

@mmalisper
and I designed Gravity to push the boundary of what's possible for a database. Gravity compiles query plans directly to native code Also, pgrcolumnar now supports all Postgres indexes Blog post: Code:
11 likes

@mmalisper
Try the browser demo: Keep standard PostgreSQL as the source of truth for data you can't afford to lose. Use the beta for test workloads or analytical replicas, and report bugs or differences from Postgres on GitHub
6 likes

@mmalisper
Thanks to our early users, including Kanu, PGX and Folio, for building with @pgrustdb @TRYKANU @itskarangrover @alxshp
6 likes

@tobias_petry
@pgrustdb Funny to post that when v0.3 has been removed from the ClickHouse benchmarks because the implementation was cheating. Oh and it couldn't run anything except the benchmarked queries.. But yeah sure, v0.4 will be honest. Pinky promise 🤞
8 likes

@mmalisper
@pgrustdb We weren't cheating. I wrote an explanation here:

@pgrustdb
Giving a talk on pgrust next week in SF
3 likes

@JasonSeibel
@pgrustdb much more coming soon
2 likes

@chenzhangreal
@pgrustdb 3x faster than clickhouse is a wild claim. would love to see the benchmark behind that.
2 likes

@bypoddar
@pgrustdb lfg guys!
1 like

@drewhariri
@pgrustdb Let’s goooo @JasonSeibel
1 like

@ryanmelehan
@pgrustdb Looks cool! I'm curious how you're able to beat DuckDB on OLAP queries? Was this tested against pg_duckdb?
1 like

@mmalisper
@pgrustdb This was against normal duckdb The biggest difference is that because we have a JIT compiler. Every other mainstream DB uses an interpreter to execute queries. Because of the JIT compiler, we're able to generate highly optimized assembly at query time
3 likes

@SamuelScheit
@ryanmelehan @pgrustdb Postgres would beg to differ

@mmalisper
@ryanmelehan @pgrustdb The Postgres JIT compiler does 1% of what we do. Postgres uses the JIT compiler in two places: expression evaluation and tuple deforming. On top of that it has 50ms of overhead so you can't use it in most places We JIT compile the full SQL query end to end and do it in <1ms
2 likes

@JasonSeibel
@pgrustdb also check out our discord where you can shape what we build next and hear about what we're working on before we share it anywhere else:

@jakalinov
@pgrustdb congrats on the sick launch!

@dorianj
@pgrustdb interested in the deep dive on the memory scheduler btw buffer cache and cxn work mem

@bensicard
@pgrustdb very tempted to try it out

@mmalisper
@pgrustdb If you reach out over twitter dm or on discord, we would be happy to work with you to get it set up
1 like













