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 1rZZYq-005FKP-KX for pgsql-general@arkaria.postgresql.org; Mon, 12 Feb 2024 16:53:41 +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 1rZZXp-00BUWm-Hg for pgsql-general@arkaria.postgresql.org; Mon, 12 Feb 2024 16:52:37 +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 1rZZXp-00BUWd-72 for pgsql-general@lists.postgresql.org; Mon, 12 Feb 2024 16:52:37 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rZZXm-006Ocq-Jo for pgsql-general@lists.postgresql.org; Mon, 12 Feb 2024 16:52:35 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 41CGqVuV2238637; Mon, 12 Feb 2024 11:52:31 -0500 From: Tom Lane To: Karsten Hilbert cc: pgsql-general@lists.postgresql.org Subject: Re: Safest pgupgrade jump distance In-reply-to: References: Comments: In-reply-to Karsten Hilbert message dated "Mon, 12 Feb 2024 17:07:47 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2238635.1707756751.1@sss.pgh.pa.us> Date: Mon, 12 Feb 2024 11:52:31 -0500 Message-ID: <2238636.1707756751@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Karsten Hilbert writes: > Am Mon, Feb 12, 2024 at 09:31:50AM -0500 schrieb Ron Johnson: >> https://www.postgresql.org/docs/16/pgupgrade.html >> "pg_upgrade supports upgrades from 9.2.X and later to the current major >> release of PostgreSQL, including snapshot and beta releases." > Just to be sure: it should be stressed that the binaries of > the later version (16 in OPs case) should be used to run the > upgrade, right ? Right. Another thing worth pointing out here is that with such a large jump distance, you'd better test application compatibility before making the change on your production database. There are likely to be a few gotchas. regards, tom lane