The single biggest change @JasonSeibel and I have made for @pgrustdb is switching from a…
This is a dev post classified by Jev as Databases (a launch), kept by the Dev Radar because it carries real work, not commentary.
The single biggest change @JasonSeibel and I have made for @pgrustdb is switching from a process per connection model to a thread per connection model. This has a ton of implications. pgrust is more reliable, faster, and needs less memory because we're using threads. Our eventual goal is to make connections so cheap, that you don't need to run an external connection pooler like pgbouncer in front of your database.
Posted by Michael Malis (1.1k followers) 18 h ago · 103 likes · 9.3k views · view the original post on X. Kept by the Dev Radar as Databases.
More dev work like this
- Enterprise data can contain the answers you need, but it's often difficult to query… — @freeCodeCamp
- Nathan: — @benswerd
- Snowflake Adaptive Compute predicts each query’s performance curve before execution. — @Snowflake
- Reporting across SQL, spreadsheets, and APIs shouldn’t require a custom BI build. — @DanKornas
- Zero-Copy Interactive lets Interactive warehouses query your existing standard Snowflake… — @Snowflake
- Apache Spark 4.2 is out, and it adds vector primitives to Spark SQL: distance and… — @ApacheSpark
- Stop sending your coding agent into vector-search docs without a map. — @DanKornas
- Text classification in MotherDuck just got ~50x faster at ~1% of the cost. — @motherduck
Every post is read and classified by Jev (TypeSafe): what it is, which market it belongs to, and whether the link is a real tool. 20.7k posts from 4.9k X accounts over the last 21 days, 2.4k tools, 12 markets. Collected every 5 minutes, fully re-ranked every hour — last update 2026-09-22 08:21 UTC. Full method.