PostgreSQL 18 Released • Hacker News Board

Re: PostgreSQL 18 Released

#21

Post by jeltz » Thu, Sep 25, 2025, 10:04 PM UTC

ktosobcy wrote: post #10

jeltz wrote: post #6

Earlier quoted context omitted.

That is mostly an issue with the official docker image, not a PostgreSQL issue. Upgrading to a new major is easy if you use the Debian packages and is fine with a couple of minutes downtime. There is no reason a docker image could not do the same. The issue with PostgreSQL which the Debian packages handle fine but the Docker Hub's image does not is that you need both the executables for the old and the new major vers…

I'm fully aware why it's an issue with official image. But even with debian (or any other "packaging") there are hoops to be hopped through due to said missing upgrade handling which IMHO is very annoying. They do handle minor versions upgrade so the code handling upgrading is there but devs seems to be quite adamant against adding major version upgrade. I (well, a lot of people judging from votes and comments in htt…

I suggest you look into what pg_upgrade actually does because the "code handling upgrading" does not exist other than as pg_upgrade. And writing it would be a ton of work and would likely halt a lot of innovation in PostgreSQL and make it no longer a competitive database unless someone does a major re-architecting of PostgreSQL which likely would break all extensions.

The issue causing it is how PostgreSQL has implemented the system catalog.

Re: PostgreSQL 18 Released

#22

Post by jeltz » Thu, Sep 25, 2025, 10:08 PM UTC

ksec wrote: post #9

jeltz wrote: post #8

Earlier quoted context omitted.

I don't think so. What do you need it for if I may ask? If some people actually need a patch it is much more likely to get people working on it to make it committable.

TAM is prerequisite for OrioleDB. And I am guessing OP like me is looking forward to orioledb being used as default or even upstreamed.

OrioleDB is very far from being usable as default or upstreamed. Nobody is working on this right now.

Re: PostgreSQL 18 Released

#23

Post by kiwicopple » Fri, Sep 26, 2025, 8:41 AM UTC

jeltz wrote: post #22

ksec wrote: post #9

Earlier quoted context omitted.

TAM is prerequisite for OrioleDB. And I am guessing OP like me is looking forward to orioledb being used as default or even upstreamed.

OrioleDB is very far from being usable as default or upstreamed. Nobody is working on this right now.

fwiw, we have a team working on OrioleDB at supabase, with the plan to get to GA later this year or early next year. we'll continue to submit patches upstream for the TAM, and of course that will take as long as it takes for the community to accept them. Our focus right now reliability and compatibility, so that the community can gain confidence in the implementation