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 <pgsql-general-owner+archive@lists.postgresql.org>)
	id 1uY8Y0-001f6j-S7
	for pgsql-general@arkaria.postgresql.org; Sat, 05 Jul 2025 19:27:40 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-general-owner+archive@lists.postgresql.org>)
	id 1uY8Xx-009Ukl-NY
	for pgsql-general@arkaria.postgresql.org; Sat, 05 Jul 2025 19:27:38 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1uY8Xx-009UkS-DK
	for pgsql-general@lists.postgresql.org; Sat, 05 Jul 2025 19:27:38 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by magus.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1uY8Xv-005wO6-1Y
	for pgsql-general@lists.postgresql.org;
	Sat, 05 Jul 2025 19:27:37 +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 565JRXHS070969;
	Sat, 5 Jul 2025 15:27:34 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Pierre Fortin <pf@pfortin.com>
cc: pgsql-general@lists.postgresql.org
Subject: Re: pg_upgrade: can I use same binary for old & new?
In-reply-to: <20250705151928.3a9ea7b1@pfortin.com>
References: <20250705125207.31b4d475@pfortin.com> <b558441b-0bd8-4cfb-aa4c-64fdcb530531@aklaver.com> <20250705142416.06e99667@pfortin.com> <65041.1751740220@sss.pgh.pa.us> <20250705151928.3a9ea7b1@pfortin.com>
Comments: In-reply-to Pierre Fortin <pf@pfortin.com>
	message dated "Sat, 05 Jul 2025 15:19:28 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <70967.1751743653.1@sss.pgh.pa.us>
Date: Sat, 05 Jul 2025 15:27:33 -0400
Message-ID: <70968.1751743653@sss.pgh.pa.us>
List-Id: <pgsql-general.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-general@lists.postgresql.org>
List-Owner: <mailto:pgsql-general-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-general>
Archived-At: <https://www.postgresql.org/message-id/70968.1751743653%40sss.pgh.pa.us>
Precedence: bulk

Pierre Fortin <pf@pfortin.com> writes:
> OK...  I failed to mention I have several databases in this cluster; so
> digging into pg_dumpall, I see:
>    --binary-upgrade
>     This option is for use by in-place upgrade utilities. Its use for
>     other purposes is not recommended or supported. The behavior of the
>     option may change in future releases without notice.

That is infrastructure for pg_upgrade to use.  Do not try to use it
manually; it won't end well.

> All my DBs are static (only queries once loaded). Assuming the dumpall
> file fits on one of my drives:
>  pg_dumpall -f <path>/PG.backup -v 
> appears to be all I need? pg_dump has compression by default; but I don't
> see compression with dumpall other than for TOAST.

I would try that first before messing with compression.  If it doesn't
fit, you'll need to do pg_dumpall --globals-only (mainly to capture
your role definitions) and then pg_dump each database into a separate
compressed file.

			regards, tom lane