Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t9eIa-00BTcB-5E for pgsql-general@arkaria.postgresql.org; Sat, 09 Nov 2024 05:46:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1t9eIW-00GRLU-Bx for pgsql-general@arkaria.postgresql.org; Sat, 09 Nov 2024 05:46:12 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t9eIW-00GRLE-1L for pgsql-general@lists.postgresql.org; Sat, 09 Nov 2024 05:46:12 +0000 Received: from cloud.gatewaynet.com ([185.90.37.94]) by makus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t9eIS-000vP2-Ez for pgsql-general@lists.postgresql.org; Sat, 09 Nov 2024 05:46:11 +0000 Message-ID: <83d29a1f-9da6-4f6f-a6be-97a7749a4fd3@cloud.gatewaynet.com> Date: Sat, 9 Nov 2024 07:46:04 +0200 MIME-Version: 1.0 Subject: Re: Can we directly upgrade postgresql from 13 to 15.4 To: pgsql-general@lists.postgresql.org References: Content-Language: en-US From: Achilleas Mantzios In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Στις 8/11/24 20:16, ο/η Christophe Pettus έγραψε: > >> On Nov 8, 2024, at 10:12, jayesh thakare 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. >