Aug 9, 2026 · 13 min · 9 segments
In this episode of Scaling Postgres, we discuss pgrust running analytical queries 300 times faster than Postgres, how to speed up distinct count, Xata podcast and massively parallel backups. To get…
Creston JamisonHost

This is from malicebird.me. And he said, last week we released version 0.2 of PGRust, 10 times faster than the previous version.

And he says most of this performance difference is due to the query engine, so he's going to be talking about that.

So basically they optimize pgRust query engine to use less CPU and less memory bandwidth than Postgres when processing the same queries.

Now he has an example here where he shows a summarization query summarizing 500 million numbers that takes 20 seconds.

But then he says for comparison, here's how you do it in Rust, which is entirely apples to oranges.

The apples to apples comparison would be what is the C code performance of this and what is the Rust performance of this? Now he does say this example isn't an apples to apples, but is pretty apples to oranges.

So now he says that's an indication of all the overhead to process a SQL query and do those summarizations to get back the end result.

And the key feature of the volcano model is the next method, which is to return a single row.

So while this executor is very simple, and he says this code is close to what Postgres does, it adds a lot of overhead.


This is from malicebird.me. And he said, last week we released version 0.2 of PGRust, 10 times faster than the previous version.

And he says most of this performance difference is due to the query engine, so he's going to be talking about that.

So basically they optimize pgRust query engine to use less CPU and less memory bandwidth than Postgres when processing the same queries.

Now he has an example here where he shows a summarization query summarizing 500 million numbers that takes 20 seconds.

But then he says for comparison, here's how you do it in Rust, which is entirely apples to oranges.

The apples to apples comparison would be what is the C code performance of this and what is the Rust performance of this? Now he does say this example isn't an apples to apples, but is pretty apples to oranges.

So now he says that's an indication of all the overhead to process a SQL query and do those summarizations to get back the end result.

And the key feature of the volcano model is the next method, which is to return a single row.

So while this executor is very simple, and he says this code is close to what Postgres does, it adds a lot of overhead.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.