Nov 19, 2026 · 53 min · 10 segments
**Tip: watch on YouTube. Since episode 193, the video shows charts and illustrations as we talk.** https://youtu.be/VcDU-NRE3hI Michael, Nik, and Kirk discuss…
Nikolay SamokhvalovHost
Kirk WolakGuest
Michael ChristofidesHostSo today, I guess we have impossible task because November 19 is very well known release date, but for very different software.
Except some few Postgres nerds, right? Because GTA 6 is being released on November 19.
And we're here to discuss Postgres 19, right? Yeah, that's funny, right? Wow.
In the current GTA release cycle, when would GTA 19 come out? Like a couple of hundred years? I don't know.

Well, I think the first thing we need to mention is Postgres 19 is ready for release.

They've updated, they've committed the changes from release candidate, the PG-9 version 19.

Did you slow it down by, you know, go working on your own project? Did you slow down Postgres or something? Seems a little late.
Yeah, no, nothing to do with me, but I actually did want to thank the people that had slowed it down.
I know we normally get, for the last few years, it's been very, very reliably in September.
And the project aims for an annual release cycle, right? Like an annual major version upgrades and then quarterly minor version upgrades, plus some security fixes that have come off cadence.
And this is quite the shift, right? September, October, November, a couple of months later.
I know there's been tons of articles about this, and you've probably discussed it.
But I think most of the articles have skewed a little bit negative, like why is it such a bad thing that it's delayed? But I wanted to say I'm really pleased that people have, firstly, Prioritize the security fixes.
I think that was like the number one reason that this got delayed because a lot of the Important like a lot of the the key committers were tied up Because they're also part of the security team and we've seen in the last two minor versions like 70 plus CVEs so that's a lot of work and And then obviously on top of that, there's been, I mean, I think the reason we've got the CVs is people using LLMs to find them.
And yeah, I think... it's much better that we've delayed this and got those fixed as well as I know the negativity is probably mostly about the reverts that happened but I think I've seen several posts I don't know if you two agree with the analysis I've seen several posts that have argued actually the reverts are very similar in number maybe a little bit bigger in size than previous versions they just happened later in the cycle so it seemed worse
When I was reporting some bugs found with VR, of course, I felt like if I keep pushing, I can do more damage and more things will be reverted.
It was part of differential integrity stuff, and another part was the last one I was...
So today, I guess we have impossible task because November 19 is very well known release date, but for very different software.
Except some few Postgres nerds, right? Because GTA 6 is being released on November 19.
And we're here to discuss Postgres 19, right? Yeah, that's funny, right? Wow.
In the current GTA release cycle, when would GTA 19 come out? Like a couple of hundred years? I don't know.

Well, I think the first thing we need to mention is Postgres 19 is ready for release.

They've updated, they've committed the changes from release candidate, the PG-9 version 19.

Did you slow it down by, you know, go working on your own project? Did you slow down Postgres or something? Seems a little late.
Yeah, no, nothing to do with me, but I actually did want to thank the people that had slowed it down.
I know we normally get, for the last few years, it's been very, very reliably in September.
And the project aims for an annual release cycle, right? Like an annual major version upgrades and then quarterly minor version upgrades, plus some security fixes that have come off cadence.
And this is quite the shift, right? September, October, November, a couple of months later.
I know there's been tons of articles about this, and you've probably discussed it.
But I think most of the articles have skewed a little bit negative, like why is it such a bad thing that it's delayed? But I wanted to say I'm really pleased that people have, firstly, Prioritize the security fixes.
I think that was like the number one reason that this got delayed because a lot of the Important like a lot of the the key committers were tied up Because they're also part of the security team and we've seen in the last two minor versions like 70 plus CVEs so that's a lot of work and And then obviously on top of that, there's been, I mean, I think the reason we've got the CVs is people using LLMs to find them.
And yeah, I think... it's much better that we've delayed this and got those fixed as well as I know the negativity is probably mostly about the reverts that happened but I think I've seen several posts I don't know if you two agree with the analysis I've seen several posts that have argued actually the reverts are very similar in number maybe a little bit bigger in size than previous versions they just happened later in the cycle so it seemed worse
When I was reporting some bugs found with VR, of course, I felt like if I keep pushing, I can do more damage and more things will be reverted.
It was part of differential integrity stuff, and another part was the last one I was...
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.