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 1sy7X3-00EVHQ-Kx for pgsql-admin@arkaria.postgresql.org; Tue, 08 Oct 2024 10:33:33 +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 1sy7X0-006tyQ-QQ for pgsql-admin@arkaria.postgresql.org; Tue, 08 Oct 2024 10:33:30 +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 1sy7X0-006tvi-Aa for pgsql-admin@lists.postgresql.org; Tue, 08 Oct 2024 10:33:30 +0000 Received: from mail-wr1-x436.google.com ([2a00:1450:4864:20::436]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sy7Wx-0036dz-PW for pgsql-admin@lists.postgresql.org; Tue, 08 Oct 2024 10:33:29 +0000 Received: by mail-wr1-x436.google.com with SMTP id ffacd0b85a97d-37cc5ba03c6so328664f8f.1 for ; Tue, 08 Oct 2024 03:33:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1728383606; x=1728988406; 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=7ZuqvxWPsE3bzijB0wP8fm6IgEvdHKKi56j8G2xTlDs=; b=is1/QTrIdRoVsW9H+oQDTPqlu7td5/n4NRLGtANgcxoT2B6I2yC4jXt8mXpNpTpg5Y bgKTZPvHMrbxtyjHadfA5EilJWMIBQuUmSQdQywkd+lqF2rJa2BafXjJsLpCwxx19ClU ywGiv7uT+95NSUrZCs2UmbubwOonOJd+PaOYYnVA4MtcViFtVxlPu8JdVFgCHYTAwvsM GqzkrxCEZcYh/J4IsB/m7EjmO/mNUz5lNg9pfCosi5X9zsz94i0APJUt0fCPlgshQWwa zmr4CjbexIdQqOkiuCiMivLv0aEd0qPs6MDks5hOv0ScnpLBjcGB7+ihWkFBHVo5aJe5 mkBw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1728383606; x=1728988406; 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=7ZuqvxWPsE3bzijB0wP8fm6IgEvdHKKi56j8G2xTlDs=; b=Zr59Kss5khj/wu0hOCFBXzpDS7r1rlVLnpJpJeM250qQ6HEhSVje15xannGK4qp1vv xnNE3FH4yKUc2CnE0a2aHHYO8VgzMvtEmGLjy5GeMzIOd6oA/7qmh9z2ls1PFct8pCio 9RNaCxcuB+sp4Q2Z6qlsWEwfYdvX5EskLfBqK1vlu/KfezIXLbVMnCMx4NPXWizU3p3B 3bTWU/bIJuw335b7GVUqv+BY7N/778E+Znpj+YwpHGU36aXakbeTgbUN2htExOsMhyfB 9EeMF9cAa+1SDq4F3bo57pHZqVfM7pGqehb+Coss5bbNzOR6QCh+MWSaY4zFkzo0uklL TMiQ== X-Gm-Message-State: AOJu0Yxo5Rrr8X7oWcr9XONryJ1IoIVvfwOT4i2MGFYLUoDxzCuWObA1 hfFpqMvu+TpOr2f3/dvR/Q5Sb0IAS1XzSPWqyn2hfFruJn71nkmAnCuVoN2Ki1nCS5xC/U9xxKQ fU7NSwsoMCA3snrGjL3JmOBVyMNU= X-Google-Smtp-Source: AGHT+IEiuXuZuhCKvY8mcXZdqX0wiIzjbHIPlpNdqsVXY6GYvMIN3D3inUw7eIupd87ZFSdydb5HaIwb/A0czUXqel4= X-Received: by 2002:a5d:588a:0:b0:37c:f92f:c58b with SMTP id ffacd0b85a97d-37d0e7d892emr3784424f8f.7.1728383606056; Tue, 08 Oct 2024 03:33:26 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Sameer Malve Date: Tue, 8 Oct 2024 16:03:17 +0530 Message-ID: Subject: Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. To: Zaid Shabbir Cc: pgsql-admin@lists.postgresql.org, Sameer.Malve@mobileum.com Content-Type: multipart/alternative; boundary="000000000000dff50b0623f4aaa0" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000dff50b0623f4aaa0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Zaid, Does this Upgrade command stand true in case of postgres upgrade between community (PGDG) to RHEL? Regards, Sameer Malve On Tue, Oct 8, 2024 at 3:24=E2=80=AFPM Zaid Shabbir = wrote: > Hello Sameer, > > For upgrade you can also use quick upgrade scripts > > /usr/pgsql-16/bin/postgresql-16-setup check_upgrade > > /usr/pgsql-16/bin/postgresql-16-setup upgrade > > > Above commands are helpful to upgrade from 15 to 16, in case someone want= s > to upgrade from -2 older version then some minor adjustments required in > setup script. > > > > Regards, > > Zaid > > On Tue, Oct 8, 2024 at 1:24=E2=80=AFPM 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 >> > --000000000000dff50b0623f4aaa0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi=C2=A0Zaid,

Does this Upgrade command= stand true in case of postgres upgrade between community (PGDG) to RHEL?

Regards,
Sameer Malve

On Tue, Oct 8,= 2024 at 3:24=E2=80=AFPM Zaid Shabbir <zaidshabbir@gmail.com> wrote:
Hello=C2=A0Sameer,

For upgrade you can also use quick upgrade scripts

<= /div>

/usr/pgsql-16/bin/postgresql-16-setup check= _upgrade

/= usr/pgsql-16/bin/postgresql-16-setup upgrade


Above commands are h= elpful to upgrade from 15 to 16, in case someone wants to upgrade from -2 o= lder version then some minor adjustments required in setup script.



Regards,

Zaid


On Tue, Oct 8, 2024 at 1:24=E2=80=AFPM Sameer Malve <malvesameer@gmail.com> wr= ote:
Hi Team,

We are trying to perform the Major versio= n 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 belo= w issue.

As the binaries are getting upgraded in-p= lace `/usr/bin` hence=C2=A0while performing pg_upgrade we are not getting t= he older binaries.

pg_upgrade command is as follow= s.

[2= 024-10-04 11:18:47]=C2=A0 $ /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= ] =C2=A0
[2024-10-04 11:19:19] =C2=A0You must identify the directory whe= re the old cluster binaries reside.
[2024-10-04 11:19:19] =C2=A0Please u= se the -b command-line option or the PGBINOLD environment variable.
[202= 4-10-04 11:19:19] =C2=A0Failure, exiting
=C2=A0
<= div>
Regards,
Sameer Malve
--000000000000dff50b0623f4aaa0--