KW Kirk Wolak Kirk Wolak On Postgres FM

“I've never once had pushing a bad position turn out beneficial in the tech world in my life. So I prefer to pull back a bit and regroup and come back later. … If we lose stability, then we're going to lose the mind share in this industry. We don't become people's first choice on new projects.”

Postgres FM · Hands-On Engineering Podcasts · November 2026

“I've never once had pushing a bad position turn out beneficial in the tech world in my life. So I prefer to pull back a bit and regroup and come back later. … If we lose stability, then we're going to lose the mind share in this industry. We don't become people's first choice on new projects.” — Kirk Wolak, Postgres FM

Context

Kirk Wolak defends the Postgres committers' decision to revert unfinished features late and delay the release, at a time when the project is handling far more CVEs than usual with the same number of committers.

Transcript

Postgres FM Around 05:59 into the episode
Nikolay Samokhvalov

…to stop pushing. And my hypothesis is some guys also stopped pushing too much just to let just to let the feature list stabilize. 100% sure, 100% sure we could find more bugs. We just didn't pull more attention to it. So right after release, I'm going to find more bugs. Yeah. And others will do.

Michael Christofides

Yeah, go on, Herc.

Kirk Wolak

Yeah, yeah. But I just want to back up the truck. So as we were moving into the date to go live, there was a big revert fest, right? And usually there's a revert fest early on in February. I think that's when Andre coined the phrase, or I heard it the first time. So I'll give him credit, but it made me laugh out loud. We have commit fests and then we had a revert fest where, yeah, these really aren't ready. They're going to need more time. Anyways, but they pulled those and they were in a release candidate kind of level and they pulled and they pulled a handful. And I just want to give them credit because, look, you don't push bad positions. Okay. I've never once has pushing a bad position turned out beneficial in the tech world in my life. So I prefer to pull back a bit and regroup and come back later. And that's what they did. And the catch up was we have the same number of committers. We have like double the number of ideas and patches coming through. And now we had something like 10 or 20 X the number of CVEs in the same year. Like that's insane. There's no way the…

Nikolay Samokhvalov

So Reverfest big wave started with this scary scary list, right? No, from Robert Haas. Yeah. It was from Thomas Wondra, the blog post about that. It's like maybe the same, but problems found later and reward happens later. So the question is how to find problems earlier. And this tiny project, PG…

Michael Christofides

There's an argument that LLMs got significantly better at an awful time in the Postgres release cycle. Like that, if you think about when feature freezes, it feels like it times very, very well with things like Opus 5.5. And I think a lot of people getting access to quite cheap, very, very advanced…

Nikolay Samokhvalov

Similarly, but Opus 4.8 was already quite good and could find a lot. It's just the question is, can you just allocate a lot of resources to it and so on? And also there is time for reaction and change habits and so on. And also there are guys who had zero or one. I saw a couple of guys who…

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.

More from Postgres FM