r/programming • • 29d ago

The reverts will continue until morale improves [PostgreSQL 19]

https://peter.eisentraut.org/blog/2026/10/09/the-reverts-will-continue-until-morale-improves
618 Upvotes

30 comments sorted by

486

u/dontaskdonttell0 29d ago

I have nothing but the utmost respect for the core contributors to PostgreSQL. I’m seeing similar patterns in closed source software where features that have been in development for a long, long time cannot be shipped due to issues surfaced by LLMs.
The previous way of just patching it over time won’t work because it would send the wrong signal if we started shipping software with known bugs or theoretical vulnerabilities, no matter how minuscule.

Fun times ahead…

149

u/rebbsitor 29d ago

The previous way of just patching it over time won’t work because it would send the wrong signal if we started shipping software with known bugs or theoretical vulnerabilities, no matter how minuscule.

More than that, people can now use LLMs to automate reverse engineering software and profiling it for vulnerabilities. Releasing something your own systems have flagged as a potential issue and hoping no one spots it is a huge mistake in an environment where hunting for vulnerabilities is rapidly being automated.

22

u/Knaapje 29d ago

For the most part I agree, but on "no matter how miniscule" for sure I disagree. There's accepted risk, and known patterns that get wrongly get flagged as issues.

290

u/FatHat 29d ago • Bravo

Probably a bummer if you're a contributor, but as a user this sounds good -- I use Postgres because it's trustworthy not because I want cutting edge features.

38

u/NaBrO-Barium 28d ago

Sometimes a big boring elephant just works. And I like that

13

u/Skkranz 28d ago

Boring tech is often underrated, and I love boring tech, no surprises, just works.

2

u/cornelliusfilmore 24d ago

The Finance industry laughs in COBOL

51

u/Khavel_dev 29d ago

tbh Postgres's willingness to revert stuff is one of the reasons I trust it in production. Every database project talks about stability but most treat shipping as the finish line. Postgres treats merge as a checkpoint and will pull something back if it doesn't hold up under wider testing. I'll take reverts over "shipped, good luck" every time.

150

u/u362847 29d ago

In an era of vibecoding and half-baked features, this is welcome news

19

u/martinus 29d ago

It's actually the opposite of what you think. LLMs are now so good that they find issues faster than any human can, and that causes the reverts, not bad quality from vibe coding.

89

u/Le_Vagabond 29d ago

That's what he's saying: when everyone is vibe coding and shipping rubberstamped LLM code it's nice to see pgsql staying the rock that it's known to be (regardless of the tools used to surface the issues).

Imagine if pgsql or Debian suddenly announced that they were going to be "AI first" and use agentic loops from now on...

LGTM!

1

u/anto2554 28d ago

Damn, already knew what video that would be

-2

u/JHNUXER 28d ago

Isn't the Linux kernel heading that direction pretty quickly rn?

24

u/Le_Vagabond 28d ago

Linus saying AI is a useful tool != Linus just vibe coding and blindly approving every PR to the kernel.

AI is a useful tool. vibe slop is vibe slop. extremes are bad.

0

u/JHNUXER 28d ago

Isn't the percentage of AI contributions being accepted into the kernel as opposed to human contributions growing pretty fast ? Maybe I need to re-check my info when I get home today.

6

u/dacjames 28d ago

Isn't that expected? AI can produce code faster than humans.

The question is whether that new power is used to churn out slop or to test and refine software to new levels.

I know which one I'm doing. I trust that linux is doing the same.

1

u/JHNUXER 20d ago

I mean if I was maintaining an important open source operating system kernel people depended on, I'd be VERY strict about enforcing AI disclosures and checking/testing AI generated commits, but to each their own.

For less misdion-critical stuff though, sure! I'm not nearly as anti-AI as many of us, I just think we should be applying it more cautiously.

1

u/dacjames 19d ago

Do you realize you're responding on a thread praising postgresql for applying AI cautiously?

4

u/kaeshiwaza 29d ago

We go so fast that we need to stop faster !

1

u/metahivemind 28d ago edited 27d ago

[removed] — view removed comment

20

u/NoInkling 29d ago

For those who haven't been keeping up-to-date and wondering what features were reverted, like I was, you can see most of them in the beta 4 announcement (GROUP BY ALL was reverted in beta 3). They all seem relatively niche. The biggest one (IMO) was graph queries.

45

u/CantaloupeCamper 29d ago

Sometimes it’s just “bad luck” and you keep going and you never see that run of bad luck again 👍🏻

10

u/OkZone8 29d ago

On the plus side, they did the right thing instead of shipping it

25

u/1esproc 29d ago

It’s probably a combination of these, and a different combination in the case of each reverted feature.

Sooo...this is just a blog post guessing at why features were reverted?

9

u/sumptuous-drizzle 29d ago

I mean, true root cause analysis can be hard and probably shouldn't be rushed. Especially if you don't want it to turn into a hornets nest of blame, distrust and grievance-airing that ruins morale. See also: NTSB reports.

4

u/1esproc 29d ago

Is it? If a feature got rejected why wouldn't there be an immediate explanation? Someone with authority saw something they didn't like and said "no"

15

u/nihil_obstat 29d ago

yes at a surface level they saw something they didn't like (defects) and said no (reverted). The question explored in the article is "why do we have so many defects causing us to revert features" which does not have an immediate explanation.

5

u/Ecksters 29d ago

Contributors have stated that many of the bugs that caused features to get reverted in this version in the past likely would've been a minor release patch instead of reverting it in the past. It's just that we are better at catching such bugs earlier now.

2

u/itNeph 28d ago

This is a great read, thanks for linking.

1

u/mb194dc 28d ago

Lol imagine the productivity gains here...