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 1uY7GQ-001Koi-0F
	for pgsql-general@arkaria.postgresql.org; Sat, 05 Jul 2025 18:05:26 +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 1uY7GN-008hsn-W5
	for pgsql-general@arkaria.postgresql.org; Sat, 05 Jul 2025 18:05:24 +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 <pf@pfortin.com>)
	id 1uY7GN-008hsf-Kn
	for pgsql-general@lists.postgresql.org; Sat, 05 Jul 2025 18:05:24 +0000
Received: from mail94.out.titan.email ([54.235.81.176])
	by magus.postgresql.org with esmtps  (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <pf@pfortin.com>)
	id 1uY7GL-005vkE-1H
	for pgsql-general@lists.postgresql.org;
	Sat, 05 Jul 2025 18:05:23 +0000
Received: from localhost (localhost [127.0.0.1])
	by smtp-out.flockmail.com (Postfix) with ESMTP id B08F0100012
	for <pgsql-general@lists.postgresql.org>; Sat,  5 Jul 2025 18:05:19 +0000 (UTC)
DKIM-Signature: a=rsa-sha256; bh=MvB1zG9021VhtlLR6yhe2JmNixp41DjomX2NJxJ1w7A=;
	c=relaxed/relaxed; d=pfortin.com;
	h=to:subject:mime-version:from:in-reply-to:references:date:message-id:from:to:subject:date:message-id:in-reply-to:references:cc:reply-to;
	q=dns/txt; s=titan1; t=1751738719; v=1;
	b=B6kbjEw0APi8b7JLKAAd84OHudSBkAaDHS6TXCWKmmBAX+dQoXZJ13GB3MSDvJryEHvFOmML
	LWYJHnk6weB1G+93ZKAWinEwvoKFBGJKK6izOcjj57+Nmhn7KW9g2BoYqZxnVwnMw6x2B+XLz2i
	wfSmikHxDDhRTSIcO0/Sisns=
Received: from pfortin.com (h194.51.155.207.dynamic.ip.windstream.net [207.155.51.194])
	by smtp-out.flockmail.com (Postfix) with ESMTPA id 6577A10000B
	for <pgsql-general@lists.postgresql.org>; Sat,  5 Jul 2025 18:05:19 +0000 (UTC)
Date: Sat, 5 Jul 2025 14:05:18 -0400
Feedback-ID: :pf@pfortin.com:pfortin.com:flockmailId
From: pf@pfortin.com
To: pgsql-general@lists.postgresql.org
Subject: Re: pg_upgrade: can I use same binary for old & new?
Message-ID: <20250705140518.784aa50e@pfortin.com>
In-Reply-To: <7265.1751735095@sss.pgh.pa.us>
References: <20250705125207.31b4d475@pfortin.com>
	<7265.1751735095@sss.pgh.pa.us>
X-Mailer: Claws Mail 4.3.1git142 (GTK 3.24.49; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-F-Verdict: SPFVALID
X-Titan-Src-Out: 1751738719557074913.20113.8725762889512967402@prod-use1-smtp-out1002.
X-CMAE-Score: 0
X-CMAE-Analysis: v=2.4 cv=c+lRQQ9l c=1 sm=1 tr=0 ts=6869695f
	a=qh1+orYxbfpu+9ysfXJjVg==:117 a=qh1+orYxbfpu+9ysfXJjVg==:17
	a=kj9zAlcOel0A:10 a=CEWIc4RMnpUA:10 a=vJnAvOe7lnr1byGQU0gA:9
	a=CjuIK1q_8ugA:10
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/20250705140518.784aa50e%40pfortin.com>
Precedence: bulk

On Sat, 05 Jul 2025 13:04:55 -0400 Tom Lane wrote:

>You cannot do pg_upgrade without a copy of the old postgres
>server binary as well as the new one.

Bummer.  Wish I had skills & time to try to overcome this...

Thanks!
Pierre