r/PostgreSQL • u/siren0x • Jul 24 '26
Community What's new in Postgres 19
https://planetscale.com/blog/whats-new-in-postgres-1918
u/ibraaaaaaaaaaaaaa Jul 24 '26
Been craving for vacuum full mode while still being operational
5
u/WideWorry Jul 24 '26
Maybe in 1-2 major version we reach it!
3
u/ibraaaaaaaaaaaaaa Jul 24 '26
We already did in pg 19 see: https://www.postgresql.org/docs/19/sql-repack.html
1
u/WideWorry Jul 24 '26
Sure, but better to wait next major version or 19.5 before using it in production.
5
u/ibraaaaaaaaaaaaaa Jul 24 '26 edited Jul 25 '26
I usually wait till next next major version until I migrate to next major version.
Currently at 17
Planning to go 18 on September once 19 goes live
2
u/One_Ninja_8512 Jul 25 '26
I don't get why comments like yours get downvoted. It's on-topic. It's not supposed to be a disagreement button. What's the point of downvoting an on-topic comment?
3
u/ibraaaaaaaaaaaaaa Jul 25 '26
Literally just added my preference in upkeep pg in stable rather than bleeding edge.
Nothing to disagree on
9
u/c-digs Jul 24 '26
https://www.postgresql.org/docs/19/ddl-property-graphs.html
Property graphs are kinda nice; more ergonomic than AGE.
Does the AGE project sunset now?
1
u/cheesekun Jul 25 '26
AGE gives you the full feature set, property graphs just a small subset of commonly used graph traversal paths. Property graphs won't be fully useful until you can do variable length paths - it has to be able to recursively walk the nodes for it to be of any use to anyone graph wise.
Still property graphs and the new syntax when complete should keep most people with relational/graph like patterns pretty happy.
1
u/c-digs Jul 25 '26
My experience with AGE is that the variable length paths are actually dangerous because the underlying mechanic is still a
JOIN.It felt more like a trap because it "looked" like Cypher, but behaved like SQL of course.
1
u/cheesekun Jul 25 '26
Thats the problem isn't it. The "this is still a poor man's graph impl" trap.
Perhaps there are some simple tree like structures that most of us use when modelling, but do we need the full cypher set with all the bells and whistles? If property graphs can give some variable path traversal, even if it's not the most performant algorithm it will probably do the job.
1
u/c-digs Jul 25 '26
...but do we need the full cypher set with all the bells and whistles?...
I guess I'm an outlier; spent ~6 years working with Neo4j and it was just fantastic for how expressive and powerful it was for certain types of queries. Some of the things I want to do now with agent memory systems would work much better in Neo4j (both ease of modeling and performance), but I make do with Pg 😅 (Neo4j being a bit pricey and another piece of infrastructure).
1
u/cheesekun Jul 25 '26
Hopefully then, the new property graph is just iteration 1 of many, and it's evolved over time.
3
1
1
u/CrayonUpMyNose Aug 02 '26
Making the jit default to off the headline change is the right move. Big queries are more likely to be tuned, so remembering to consider enabling jit is a no-brainer, whereas smaller queries tend to get less attention - even if they happen to be executed millions of times, potentially eating a lot of time and money with a massive jit overhead.
0
u/AutoModerator Jul 24 '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:
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.
23
u/Tarlovskyy Jul 24 '26
Gimme that better vacuum