Aug 23, 2026 · 11 min · 9 segments
In this episode of Scaling Postgres, we cover postgres.fm's interview of pgrust co-creator Michael Malis, pgDog vs RDS Proxy, Postgres on Kubernetes in 10 minutes and evolution to Postgres 19. To get…
Creston JamisonHost
And it's interesting he got into this because he was wanting to help people with their websites, he says, although maybe he was actually talking about web applications, and a lot of the pain problems he was hearing about was people having issues with Postgres.

So he says, "Hmm, I wonder if we should solve the problem at the source," which is re-architecting Postgres.

And several times during the interview, there was the question about, you know, something new like this is classified as not as reliable, or maybe since it was written by AI, it's not as reliable.

And I think Michael said an interesting thing, Michael Malice, that is, where you don't necessarily trust the AI coding so much, but it's the testing infrastructure you build up you have to trust, because the code ultimately has to pass all the tests that you've come up with.

And that actually highlights a limitation that Michael Malice mentioned with Postgres, in that passing the Postgres regression suite is actually a kind of a low bar, because Postgres, according to him, only has about two-thirds test coverage, so there's a fair amount of it that's not covered with tests, presumably.

Now, to address this, they have developed numerous code fuzzers to test across both the C code and the Rust code to ensure that the functions are returning the same thing, and they're even finding bugs in Postgres with this process that they are posting back to the project, which is good.

And then I was thinking the other day, you know, when would someone migrate to pgRust? And I think Michael Malice had a interesting response to that, is that he sees it as potentially starting as a read replica against your existing cluster.

At least the most recent version is much faster with analytical queries, so you could spin this up as a read replica and do analytical queries against it.

So it's not necessarily committing your OLTP transactions to it yet, but it's kind of getting your feet wet using it and seeing how it works, and then over time, that trust will presumably build as I assume this moves forward and the project continues to get more stable.

If you're interested in learning more, you can definitely listen to the podcast here or watch the YouTube video down here.

And it's interesting he got into this because he was wanting to help people with their websites, he says, although maybe he was actually talking about web applications, and a lot of the pain problems he was hearing about was people having issues with Postgres.

So he says, "Hmm, I wonder if we should solve the problem at the source," which is re-architecting Postgres.

And several times during the interview, there was the question about, you know, something new like this is classified as not as reliable, or maybe since it was written by AI, it's not as reliable.

And I think Michael said an interesting thing, Michael Malice, that is, where you don't necessarily trust the AI coding so much, but it's the testing infrastructure you build up you have to trust, because the code ultimately has to pass all the tests that you've come up with.

And that actually highlights a limitation that Michael Malice mentioned with Postgres, in that passing the Postgres regression suite is actually a kind of a low bar, because Postgres, according to him, only has about two-thirds test coverage, so there's a fair amount of it that's not covered with tests, presumably.

Now, to address this, they have developed numerous code fuzzers to test across both the C code and the Rust code to ensure that the functions are returning the same thing, and they're even finding bugs in Postgres with this process that they are posting back to the project, which is good.

And then I was thinking the other day, you know, when would someone migrate to pgRust? And I think Michael Malice had a interesting response to that, is that he sees it as potentially starting as a read replica against your existing cluster.

At least the most recent version is much faster with analytical queries, so you could spin this up as a read replica and do analytical queries against it.

So it's not necessarily committing your OLTP transactions to it yet, but it's kind of getting your feet wet using it and seeing how it works, and then over time, that trust will presumably build as I assume this moves forward and the project continues to get more stable.

If you're interested in learning more, you can definitely listen to the podcast here or watch the YouTube video down here.
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.