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 1sy7Pj-00EULm-UR for pgsql-admin@arkaria.postgresql.org; Tue, 08 Oct 2024 10:26: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 1sy7Pi-006mvu-Fl for pgsql-admin@arkaria.postgresql.org; Tue, 08 Oct 2024 10:25:58 +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 ) id 1sy7Pi-006mvL-2K for pgsql-admin@lists.postgresql.org; Tue, 08 Oct 2024 10:25:58 +0000 Received: from mail-ej1-x634.google.com ([2a00:1450:4864:20::634]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sy7Pf-003B63-NY for pgsql-admin@lists.postgresql.org; Tue, 08 Oct 2024 10:25:57 +0000 Received: by mail-ej1-x634.google.com with SMTP id a640c23a62f3a-a9953d3b2cdso23461766b.3 for ; Tue, 08 Oct 2024 03:25:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1728383155; x=1728987955; 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=u72NKblIrG335Fznez7gruv3csjUJQ/Lp5PhdzrxVxM=; b=AJMAZvmT9fWREH/5GKwxYoel6rXw3gGVJ5D8ORL1NXT2ubjGWV/vaL4c8MeY/FTP+N 50vlwWqO50l7muYTJvi7Q5Nljt9YBgT262tss7tuspj7QVQWoiU/ijDGl4ebVkOwWhV0 3B59N/cpn1hd+voZJGQOwKAhsvg6iWDc92bVZYChj71NT3W4y6PnD1lLBK5rzp3esXN4 WLN7gueyWrajlQkGqb041NxgzdoNNhkIw7IN/pGO+YPCmLg1W8NN4oxSNa4eEkeYTfJ4 VClumLG7h4B6aFEaZxEwGOdRPyTAq66/UQ8tq2EDomE3zbsoZcuKHahSllDLz/WxJyyx oOBA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1728383155; x=1728987955; 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=u72NKblIrG335Fznez7gruv3csjUJQ/Lp5PhdzrxVxM=; b=VQg6Nb0uldP4cvjrrg41pXRG9CUxFv/dfWHsladwDe7UVAd81pLrZC2bq4XpdQtWrY PjN/Z+lgJAplUg8CN6of/PoluezI3II0uhuea1wVsR8ZhBrgUSa/szvNOQWBgAi5RDNb Wvel94wvdpoD1o9QHEoRBld31fzi54EQX6Hl0Du/8vL6AdjMCyK9x6ADJOfp+BU0Z+lI DcR6ASCt2QykMl9Yxb/YwietkXkhqWt8b0uoODnydTPX2QcbgICHuExiw/+nJcR9t1Uz 1oZyW3KaiXG5mP9jwr05+6rl8LPpABE6yNpc2AHCD4LL4LcJATgEHe2XtsgXaVwua2AH uU8A== X-Gm-Message-State: AOJu0Yzj5nNA1ptJLkfDtPDZOyPmB7PZVYhQ1XOPHYtNZVqk/Uas3brc VEA9zyyKbyLOS1SCMSPlVVSvbSi8mxs8hKBbEa/lRwCNu+U60Uo1XjSBQZ04yqpokTojTZsqnRM T2uPLhvk1EGosi8dVa44/LZ1QLMY= X-Google-Smtp-Source: AGHT+IEuqmjXA9xv0nF1JhrVM94ycsL8+Spe2DazkBOTRGK50emxA2jcEMh4m3LEE2DhCY++h4UgkiZU+OenYuJ9feg= X-Received: by 2002:a17:907:a4d:b0:a80:f54c:ad68 with SMTP id a640c23a62f3a-a991bce2e1cmr678793166b.2.1728383154405; Tue, 08 Oct 2024 03:25:54 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Sameer Malve Date: Tue, 8 Oct 2024 15:55:44 +0530 Message-ID: Subject: Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. To: obi reddy Cc: pgsql-admin , Sameer.Malve@mobileum.com Content-Type: multipart/alternative; boundary="000000000000f453290623f48fc6" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000f453290623f48fc6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Obi, Just to update you, we are not using the PGDG community that provides Postgres. And the major difference between the PGDG community provided Postgres and RHEL provided Postgres is the binary files are installed in different location. in PGDG Postgres it is installed under `/usr/pgsql-16/bin` whereas in RHEL Postgres it gets installed under `/usr/bin`. hence we can't use the command you suggested. Regards, Sameer Malve. On Tue, Oct 8, 2024 at 2:02=E2=80=AFPM obi reddy = wrote: > Hi Sameer, > > Please try with this command. > > /usr/bin/pg_upgrade -b /usr/pgsql-15/bin/ -B /usr/pgsql-16/bin/ -d > /pgData/pgsql/15/data -D /pgData/pgsql/16/data -c > > If above command is not working check the below one. > > /usr/pgsql-16/bin/pg_upgrade -b /usr/pgsql-15/bin/ -B /usr/pgsql-16/bin/ > -d /pgData/pgsql/15/data -D /pgData/pgsql/16/data -c > > Thanks & Regards > Obireddy > > > > On Tue, 8 Oct 2024, 13:54 Sameer Malve, wrote: > >> Hi Team, >> >> 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 P= G >> 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. >> >> pg_upgrade command is as follows. >> >> [2024-10-04 11:18:47] $ /usr/bin/pg_upgrade -b /usr/bin/ -B /usr/bin/ -= d >>> /pgData/pgsql/15/data -D /pgData/pgsql/16/data -c >>> [2024-10-04 11:19:19] >>> [2024-10-04 11:19:19] You must identify the directory where the old >>> cluster binaries reside. >>> [2024-10-04 11:19:19] Please use the -b command-line option or the >>> PGBINOLD environment variable. >>> [2024-10-04 11:19:19] Failure, exiting >>> >> >> >> Regards, >> Sameer Malve >> > --000000000000f453290623f48fc6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi=C2=A0Obi,

Just to update you, we are= =C2=A0 not using the PGDG community that provides Postgres.=C2=A0

And the major difference between the PGDG community provide= d Postgres and RHEL provided Postgres is the binary files are installed in = different location.

in PGDG Postgres it is install= ed under `/usr/pgsql-16/bin` whereas in RHEL Postgres it gets installed und= er `/usr/bin`.

hence we can't use the command = you suggested.

Regards,
Sameer Malve.=C2= =A0



On Tue, Oct 8, 2024 at 2:02=E2=80=AF= PM obi reddy <obireddy.g1997= @gmail.com> wrote:
Hi=C2=A0Sameer,

Please try with this command.

/usr/bin/pg_upgrade -b /usr/pgsql-15= /bin/ -B /usr/pgsql-16/bin/ -d /pgData/pgsql/15/data -D /pgData/pgsql/16/da= ta -c

If above command i= s not working check the below one.

/usr/pgsql-16/bin/pg_upgrade -b /usr/pgsql-15/= bin/ -B /usr/pgsql-16/bin/ -d /pgData/pgsql/15/data -D /pgData/pgsql/16/dat= a -c

Thanks & Regard= s
Obireddy



On Tue, 8 Oct 2024, 13:54 Sameer Malve, <= ;malvesameer@gma= il.com> wrote:
Hi Team,

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 ar= e facing the below issue.

As the binaries are gett= ing upgraded in-place `/usr/bin` hence=C2=A0while performing pg_upgrade we = are not getting the older binaries.

pg_upgrade com= mand is as follows.

[2024-10-04 11:18:47]=C2=A0 $ /usr/bin/pg_upgrade -b /usr/bi= n/ -B /usr/bin/ -d /pgData/pgsql/15/data -D /pgData/pgsql/16/data -c
[20= 24-10-04 11:19:19] =C2=A0
[2024-10-04 11:19:19] =C2=A0You must identify = the directory where the old cluster binaries reside.
[2024-10-04 11:19:1= 9] =C2=A0Please use the -b command-line option or the PGBINOLD environment = variable.
[2024-10-04 11:19:19] =C2=A0Failure, exiting
<= div>=C2=A0

Regards,
Sameer Malve
--000000000000f453290623f48fc6--