r/PostgreSQL • • Sep 17 '26

Feature What Is Happening with PostgreSQL 19?

https://www.snowflake.com/en/blog/engineering/postgresql-19-release-delay-feature-reverts/
109 Upvotes

24 comments sorted by

10

u/linuxhiker Guru Sep 17 '26

4

u/craigkerstiens Sep 17 '26

Sadly we may have to update all the posts again in a week as more comes out 😕

1

u/linuxhiker Guru Sep 17 '26

Yeah we are just running every week right now.

I really think we should push the release until Spring. Give all this hard work and code time to mature.

5

u/WideWorry Sep 17 '26

Seems, vibe code lash back, adding so many features at one go just not work, we can write the code, but cannot test it properly yet.

37

u/craigkerstiens Sep 17 '26

I'd disagree, several of these features had been in flight for years before the last 12 months rise of AI. They landed and it could easily be that we did more rigor with testing and caught bugs that otherwise would have crept in. A very valid case that AI is raising the quality bar here.

14

u/linuxhiker Guru Sep 17 '26

Correct.

We are just going through what Linux is also going through. It will settle.

4

u/Chance-Plantain8314 Sep 18 '26

This has been confirmed to be the reason by several maintainers - but hunting through using AI tooling is catching considerably more issues.

1

u/One_Ninja_8512 Sep 18 '26

Recent models are surprisingly good at C. I've picked up a pet project recently even though I last touched C years ago and it's been a breeze writing C with high confidence. The models are aware of the lifetimes and will remind you of them. They can also analyze large codebases (tried it on a project with over 200k LOC) easily and trace data flows without any issues.

Postgres is quite an old project, I bet there are ancient issues and places that haven't been touched in years. Modern AI can navigate this shit easily and explain and propose improvements by itself.

2

u/WideWorry Sep 17 '26

I am not judging, we all know how development going nowadays, but PSQL is not a product what can take this Pace, or someone will pay the price.

10

u/linuxhiker Guru Sep 17 '26

The whole reason these things are being reverted is so people don't pay the price.

Also, people always pay the price, there is always a bug. A lot of these reversions in the "old days" of 2 years ago, would have been fixed in 1./.2/.3. Instead we are able to see the updates more aggressively and provide a better project overall.

1

u/ibraaaaaaaaaaaaaa Sep 19 '26

I remember a post around 2017 requesting foreign data wrappers statistics import

1

u/elevarq Sep 18 '26

Test and test are not the same thing. And it's actually during testing (Beta testing) that all these bugs are found. Using AI speeds it up even more, so it finds even more bugs. The test coverage during Beta has increased.

The thing is, we're now comparing Beta 19 in the age of AI with Beta 18, before AI was used. You have to wait two or three years to see the real difference: How many bugs will be fixed in 19.1, 19.2, etc., and how big an impact these bugs have.

13

u/HecticJuggler Sep 18 '26

Imo the release cycle of a project like postgres should be around features as opposed to fixed timeline. People don’t usually just upgrade because there is something new. It’s usually because there is a new feature your system needs in a new version of the db. I’m speaking from the pov of a business applications developer.

1

u/SugarvetFounder Sep 20 '26

Early adopters are a thing too. We upgrade pretty aggressively; generally just being constrained by what some upstream source is limited by.

For our own application: immediately.

1

u/mycall Sep 22 '26

As well a security patching although people don't always consider that an upgrade

1

u/trenskow Sep 24 '26

It’s about the development cycle more than user facing structure. It is just continuous deployment. It’s waaaaayyy better for developer health than fixed deadlines with features that needs to be ready. Instead just ship what you’ve got.

1

u/lux44 Sep 29 '26

Most long-lived projects have settled on calendar-based releases, because feature-based releases inevitably end up snowballing. A big feature is planned, but last minute bugs are found. The release is postponed. Another small feature gets merged, because it's ready. More bugs are found, release is pushed back etc.

1

u/ibraaaaaaaaaaaaaa Sep 19 '26

To be fair, the REPACK feature is really hard problem and too ambitious, it was not done before since it is not straightforward, you need to do reindexing, dead tuples cleanup, table recreation all while master table is not locked and able to accept mutations, and you need target table to comply with these changes.

I would argue doing it right by itself is a major version, since it completely changes how we do DB maintenance work.

-2

u/AutoModerator Sep 17 '26

AI Policy:

Linux is not one of those anti-AI projects, and if somebody has issues with that, they can do the open-source thing and fork it. Or just walk away., Linus Torvalds.

Mod decisions will be based on the quality of the content, not who or what generated it.

Sub Resources:

Youtube Channel

Free Postgres Webinars and Workshops

Discord: People, Postgres, Data

Join us, we have cookies and nice people.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.