Re: Can we directly upgrade postgresql from 13 to 15.4

From: Achilleas Mantzios <a(dot)mantzios(at)cloud(dot)gatewaynet(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Can we directly upgrade postgresql from 13 to 15.4
Date: 2024-11-09 05:46:04
Message-ID: 83d29a1f-9da6-4f6f-a6be-97a7749a4fd3@cloud.gatewaynet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


Στις 8/11/24 20:16, ο/η Christophe Pettus έγραψε:
>
>> On Nov 8, 2024, at 10:12, jayesh thakare <thakarejayesh700(at)gmail(dot)com> wrote:
>> Can we upgrade postresql from 13 to 15.4 directly?
>> Can we upgrade postgresql from 13 to 16 directly?
> Yes.
>
>> Ideally how many major version can we jump to from older version ?
> There's no practical limit, assuming the old version is not an ancient version of PostgreSQL (pre-9.0, say).

In which case I guess it is possible to use pg_upgrade of the maximum
version in the same supported "window". e.g. pg_upgrade of 9.4 to
upgrade from 8.3, and so forth, in iterations till someone hits the
maximum desired version.

IMHO one should pay attention with pre-PGXS modules (such as intarray) ,
I stumped across some ugly situations with that.

>
> That being said, PostgreSQL's behavior changes with every major release, and there is always the possibility of query plan changes or other surprises. It's essential to test your application thoroughly on the target version, and do dry runs of pg_upgrade.
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message David Mullineux 2024-11-09 10:10:39 Re: Performance Issue with Hash Partition Query Execution in PostgreSQL 16
Previous Message Ron Johnson 2024-11-09 05:04:09 Re: pgsql_tmp consuming most of the space.