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 1symZf-002881-8f for pgsql-admin@arkaria.postgresql.org; Thu, 10 Oct 2024 06:23:00 +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 1symZe-00CCmk-FN for pgsql-admin@arkaria.postgresql.org; Thu, 10 Oct 2024 06:22:58 +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 1symZd-00CCmc-Sy for pgsql-admin@lists.postgresql.org; Thu, 10 Oct 2024 06:22:58 +0000 Received: from mail-ej1-x62f.google.com ([2a00:1450:4864:20::62f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1symZb-0009mU-Ek for pgsql-admin@lists.postgresql.org; Thu, 10 Oct 2024 06:22:57 +0000 Received: by mail-ej1-x62f.google.com with SMTP id a640c23a62f3a-a9952a6020fso7365166b.1 for ; Wed, 09 Oct 2024 23:22:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1728541374; x=1729146174; 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=/4YQ6fK6hMd2zj3GadWMRwLBoCVsgDDSXV/gTjpyrDE=; b=ZoR/4KSdTSFA02ZI3vSyBTlonQ2yPPiKjUFO05kSCxTEsaBRmpDVwFwV0DoWZhixyO +bMo/baEnh9AqEuk/1eXrpu88BYwN7S+3LGBhrPWZ2R0UJsLBd03Jq9tiXgBF96aVHv0 fBpqkkMD2gtx7aImjL7tSA4UTeRwjWqPz7cVqP5iNZ/XcHagdKBzHcc8aZQap1EeLkNK WeMDjP87dNkMtdxv6svJLwn3oakYRdJrPUIaw1BRqF3qGX/bH0umXopSbrwUxdOF2wwk vHRt+rCqfjeB4KHjeYHJNylBMM8McQ42naWi75h68qjk0G/xckUdieQOv3xlTPuPJ6XZ tJPA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1728541374; x=1729146174; 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=/4YQ6fK6hMd2zj3GadWMRwLBoCVsgDDSXV/gTjpyrDE=; b=aSKqdtNp1EQ+2AQbZNHxA5Ye3xs94tU9xn/6UlMCEPKxsx/SUjI6DQa5hlG39B2czt 6vCM/zhVLXBD3C2LyQloEABrO0aVX2K++CGsMGWUNdwjNP04YcyanzU/57v3WOChghCc 3gQhag0qz7QxIRiHpOH7zQuKoMOaiL52h2woIwyMxqz3/cHf9fNH3er00L9k0or1dHrd n4M0ijE5BrQrjcp13MGtxXL6ayOhR4XwmM11g1HxYtM7bdiHWyRfQubdEctseHRBuDzy wCsnF0A9C7/YnNvHBr+gCXibeDzw6nunt2xE5r3WqiE1eGggowMhXLWVKiF/V+FGuxvx YycA== X-Gm-Message-State: AOJu0YwP7+r1okXU9AdL+2pbBszJ3TRqfpLTZ0PMJOUPkF5F43SBjOue h50mHOrxUfIPzxr/rEke/PZb4YLWnxATqy8miIsDHF2y84NuGtoBgAJWVf8PiToPJzmbrZ/QeX+ DPI6kHkF/fCeAvqdykl1zma+Nd/4= X-Google-Smtp-Source: AGHT+IH6InzK0IfhT0pEsIRSjERjq5Q2EuHs7dna3lIhUyIACMr9RhRGHb0s8HhYqGVEAL10vSK4CmlK2d3LrF5JYAw= X-Received: by 2002:a17:907:1c15:b0:a99:4a35:2400 with SMTP id a640c23a62f3a-a998d1fa03cmr163521266b.7.1728541373707; Wed, 09 Oct 2024 23:22:53 -0700 (PDT) MIME-Version: 1.0 References: <1910788.1728395149@sss.pgh.pa.us> In-Reply-To: From: Sameer Malve Date: Thu, 10 Oct 2024 11:52:47 +0530 Message-ID: Subject: Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. To: Tom Lane Cc: "pgsql-admin@lists.postgresql.org" , Sameer Malve Content-Type: multipart/alternative; boundary="0000000000008f405f062419668f" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000008f405f062419668f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Tom, Thanks for providing me with the correct point to look for a solution, and I was able to upgrade my cluster from PG15.6 to PG 16.4. I have few questions. 1. As I have observed, the PostgreSQL upgrade package has only the lower major version binaries. So what if I want to upgrade from PG 13 to PG 16? 2. If upgrade fails then what are the rollback steps. Do you know if it is documented somewhere? Regards, Sameer Malve On Tue, Oct 8, 2024 at 7:32=E2=80=AFPM Sameer Malve wrote: > Thanks Tom. I have installed that upgrade package rpm will go through it > and try. And would let you know incase I get stucked . > > Get Outlook for Android > ------------------------------ > *From:* Tom Lane > *Sent:* Tuesday, October 8, 2024 7:15:49 PM > *To:* Sameer Malve > *Cc:* pgsql-admin@lists.postgresql.org = ; > Sameer Malve > *Subject:* Re: RHEL certified repo provided PostgreSQL Major Version > Upgrade. > > Caution :External > > Sameer Malve writes: > > We are trying to perform the Major version upgrade on RHEL 8 using > > RHEL-certified repo `rhel-8-for-x86_64-appstream-rpms` from PG 15.6 to = PG > > 16.4 using `pg_upgrade` but we are facing the below issue. > > As the binaries are getting upgraded in-place `/usr/bin` hence while > > performing pg_upgrade we are not getting the older binaries. > > It's been more than ten years since I was responsible for Red Hat's > packaging of PG, but I think I recall that the solution in place for > pg_upgrade involved a separate postgresql-upgrade RPM containing > previous-version executables, which you were supposed to install > alongside the new version for long enough to perform the upgrade. > Whatever the details were, I'm quite certain the package's README file > contained an explanation of how to do it. Read that, do not pay > attention to people or chatbots telling you how you'd do it with some > other packaging. > > regards, tom lane > --0000000000008f405f062419668f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Tom,

Thanks for providing me with th= e correct point to look for a solution, and I was able to upgrade my cluste= r=C2=A0from PG15.6 to PG 16.4.=C2=A0

I have few qu= estions.

1. As I have observed, the PostgreSQL upg= rade package has only the lower major version binaries. So what if I want t= o upgrade from PG 13 to PG 16?
2. If upgrade fails then what are = the rollback steps. Do you=C2=A0know if it is documented somewhere?=C2=A0

Regards,
Sameer Malve


On Tue, Oct 8, 2024 at 7:32=E2=80=AFPM Sameer Malve <Sameer.Malve@mobileum.com&= gt; wrote:
Thanks Tom.=C2=A0 I have installed that upgrade package r= pm will go through it and try. And would let you know incase I get stucked = .

Get Outlook for Androi= d
From: Tom Lane <tgl@sss.pgh.pa.us>
Sent: Tuesday, October 8, 2024 7:15:49 PM
To: Sameer Malve <malvesameer@gmail.com>
Cc: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org<= /a>>; Sameer Malve <Sameer.Malve@mobileum.com>
Subject: Re: RHEL certified repo provided PostgreSQL Major Version U= pgrade.
=C2=A0
Caution :External

Sameer Malve <malvesameer@gmail.com> writes:
> We are trying to perform the Major version upgrade on RHEL 8 using
> RHEL-certified repo `rhel-8-for-x86_64-appstream-rpms` from PG 15.6 to= PG
> 16.4 using `pg_upgrade` but we are facing the below issue.
> As the binaries are getting upgraded in-place `/usr/bin` hence while > performing pg_upgrade we are not getting the older binaries.

It's been more than ten years since I was responsible for Red Hat's=
packaging of PG, but I think I recall that the solution in place for
pg_upgrade involved a separate postgresql-upgrade RPM containing
previous-version executables, which you were supposed to install
alongside the new version for long enough to perform the upgrade.
Whatever the details were, I'm quite certain the package's README f= ile
contained an explanation of how to do it.=C2=A0 Read that, do not pay
attention to people or chatbots telling you how you'd do it with some other packaging.

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 regards, to= m lane
--0000000000008f405f062419668f--