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 1uY6G1-0014hR-Fl for pgsql-general@arkaria.postgresql.org; Sat, 05 Jul 2025 17:00:57 +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 1uY6Fz-0082YG-2Z for pgsql-general@arkaria.postgresql.org; Sat, 05 Jul 2025 17:00:55 +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 1uY6Fy-0082Y8-OH for pgsql-general@lists.postgresql.org; Sat, 05 Jul 2025 17:00:55 +0000 Received: from mail-oi1-x22f.google.com ([2607:f8b0:4864:20::22f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uY6Fx-005jvb-2W for pgsql-general@lists.postgresql.org; Sat, 05 Jul 2025 17:00:54 +0000 Received: by mail-oi1-x22f.google.com with SMTP id 5614622812f47-4079f80ff0fso2099766b6e.1 for ; Sat, 05 Jul 2025 10:00:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1751734853; x=1752339653; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=J8gGknZtwhV12nvHpxaLK/zNpJUgWwVL96WX1r896GY=; b=ecxoscEw3iYg35DXnUcNMVNE2/H8moMMMD4xQssinLNBqY9ZBpc9P29PxNVQ29HFML frTzBv0hPgF3en4CI4pUTVdh2IclXcxvfCv1oVr75or1WCQOtAmUR5GjKcPldX8DeEK3 uKRobUvQZR8qBSGtFT+lkabJnChtEmKExh/Eny2AY4O9Jxy3ZZPGWAeMTKBdJSBgAV5O 4eABxxxlVh0LUJn9xG9WFLI5t9HLYoHfgPeAw46diXzmYCbkkm/2K+tS6aY8+SqCZkQ6 Qy32/42zYQt/qvfpVg5E03VS7LIWt9bBdGx1pBR/NuTBDWt1msRtkMcJA4P4aevf4CIJ QjuQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1751734853; x=1752339653; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=J8gGknZtwhV12nvHpxaLK/zNpJUgWwVL96WX1r896GY=; b=UMiXOyDfDChCodpQw0k6pDCAzubIofGlNk7PSnQ85ysGkfS1nRW6A8uMnLSmYJnpPd WZQ1MN/CKOse89O0oRepzfbGLSWrRSO/P8Bn3Y03Ujv5yz4Wz99vp1BnfM7wWOoPMiIw fc4S1JoOrZP6c3D68YKGw/5NgYe2Pq3Jd/GGG97YY679kP4VDQWHHnwoaaITo8C7GxKy ru3h8uXGd4vcrmP5qCtP6qbtiiIhF7xieuT9VKfoentzy39lfinpMrtur97x5uTzLZ5U MB3n6caYza2oU/lfTEUnRkcb6oRad1JvCmq3h58BS3AjIbSDF32JFdoMffeI5Vfwoefp XMMQ== X-Gm-Message-State: AOJu0YzScg93D5emrR+fCALoZcwfGO6CKdmIw+W0oGXg5zCJuuxprJOY utm3BiExc9ajRCXQFf1y6tIp53m87qgU28EKWi0kWYEFqNTTQkYVAbHOiNWrZA2q1Gy+wgZACDf aMVRE/rpEXz4hhsqzv1nlF7cz0LB2E/drU+Zy7F8= X-Gm-Gg: ASbGncs+AikatxPj9u+YkxaVvNY26WCdaWuWAXTpAZ3/cLvun986YuSgZ//Rd/SAI9i /j4D4LmB7Uw5d34MEFXZSU4cKz/4e1nI+YCg0KaZQicmdb3OL2l76m2ERUrI5AbKfLbFmloS/oy Lerx9WwAvyXpLMXz6gAPQnQzJyoDFPqCsoqd8TPnURVCPt1NE53P9jEeGZAYFoKo+PiTuVRiqRo xdOOMHgkVVwC+I= X-Google-Smtp-Source: AGHT+IFluYikmG3a3mEWZAtFixxLnFPAn0al7HyTJ8j4GbsI9fXL8Z2Jqjc2c4da0QOTqsVXIlCNVH04AH+2BlZ0aB0= X-Received: by 2002:a05:6808:3a1a:b0:407:39f1:ac80 with SMTP id 5614622812f47-40d029f67a2mr6021950b6e.5.1751734853120; Sat, 05 Jul 2025 10:00:53 -0700 (PDT) MIME-Version: 1.0 References: <20250705125207.31b4d475@pfortin.com> In-Reply-To: <20250705125207.31b4d475@pfortin.com> From: "David G. Johnston" Date: Sat, 5 Jul 2025 10:00:17 -0700 X-Gm-Features: Ac12FXxbhH_Muf4Hna-B5I2jD-2PWUUw7B6KKmczb8ZEjX4AM7DZWXTMtJxKvGs Message-ID: Subject: Re: pg_upgrade: can I use same binary for old & new? To: Pierre Fortin Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000a93a8a0639318d49" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000a93a8a0639318d49 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Jul 5, 2025 at 9:52=E2=80=AFAM Pierre Fortin wrote= : > If new pg_upgrade is the only binary, will both -b and -B default to it? > Maybe at minimum I may need to specify: > $ pg_upgrade -b /usr/bin -d data15 -D data17 -k > > pgsql/pgsql-18/bin > ./pg_ctl -D /var/pgsql/postgres-17 start waiting for server to start....2025-07-05 16:58:56.559 UTC [293839] FATAL: database files are incompatible with server 2025-07-05 16:58:56.559 UTC [293839] DETAIL: The data directory was initialized by PostgreSQL version 17, which is not compatible with this version 18beta1. pg_ctl: control file appears to be corrupt David J. --000000000000a93a8a0639318d49 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sat, Jul 5, 2025 at 9:52=E2=80=AFAM Pierre Fortin <<= a href=3D"mailto:pf@pfortin.com">pf@pfortin.com> wrote:
=
If new pg_upgrade is the only binary, will bo= th -b and -B default to it?
Maybe at minimum I may need to specify:
$ pg_upgrade -b /usr/bin -d data15 -D data17 -k

=C2=A0pgsql/pgsql-18/bin
>=C2=A0./pg_ctl -D= /var/pgsql/postgres-17 start
waiting for server to start....2025-07-05 = 16:58:56.559 UTC [293839] FATAL: =C2=A0database files are incompatible with= server
2025-07-05 16:58:56.559 UTC [293839] DETAIL: =C2=A0The data dire= ctory was initialized by PostgreSQL version 17, which is not compatible wit= h this version 18beta1.
pg_ctl: control file appears to be corrupt
=


David J.

--000000000000a93a8a0639318d49--