On 10/24/25 05:53, Greg Sabino Mullane wrote:
> On Thu, Oct 23, 2025 at 11:49 AM Adrian Klaver
> <adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>> wrote:
>
> I am not sure version 18 would a good choice at this time, it has
> just been released and has no bug fix releases against it yet. Given
> the
> other complications in your upgrade, OS upgrade and multi-version
> jump, I don't think you want to add a brand new version to the mix.
> Postgres
> 17 on the other hand has been out a year and has had 6 bug/security
> fixes. It is probably a more stable target version.
>
>
> I hear your concern, but I'm pretty confident in v18. Additionally, they
Which is pretty much the criteria for a GA release, confidence that it
is ready to face the general public. That is not the same thing as it
being guaranteed bug free. Only time facing the manipulations of said
public proves how many bugs there are and how bad they are.
> are on version 11 (eleven!) so obviously major upgrades are a rare
> thing, so might as well buy themselves another year. :)
Major upgrade being the operative phrase here. The OP and company are
going to face enough new hoops to jump through in the move from 11,
adding a new release to that mix is pushing it a little too far in my
estimation.
>
> Cheers,
> Greg
>
> --
> Crunchy Data - https://www.crunchydata.com <https://www.crunchydata.com>
> Enterprise Postgres Software Products & Tech Support
>
--
Adrian Klaver
adrian.klaver@aklaver.com
