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 1sy5W9-00EEoU-GU for pgsql-admin@arkaria.postgresql.org; Tue, 08 Oct 2024 08:24:29 +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 1sy5W7-0059hS-Ht for pgsql-admin@arkaria.postgresql.org; Tue, 08 Oct 2024 08:24:27 +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 1sy5W7-0059fh-3f for pgsql-admin@lists.postgresql.org; Tue, 08 Oct 2024 08:24:27 +0000 Received: from mail-ed1-x52d.google.com ([2a00:1450:4864:20::52d]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sy5W1-003A6b-SB for pgsql-admin@lists.postgresql.org; Tue, 08 Oct 2024 08:24:26 +0000 Received: by mail-ed1-x52d.google.com with SMTP id 4fb4d7f45d1cf-5c885108582so807057a12.3 for ; Tue, 08 Oct 2024 01:24:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1728375860; x=1728980660; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=olESbharqUZfyxltqb6oCdmjXv8gjlAHAvdOM2Q2nxA=; b=nctJbLHTPajgw/xI6S6jSZrnK89kIDbRZxIGmPdbGxyKmJU97yE+JyVePIwIghGdiV 8QkoEWJSDE2YBK4+EG56BpgTgVvy1V86G+RjcCu+Gor//CGL+kopDJwL+cw2Xc0gVT4p wh7FVudmc/n8eqR8JNBC/oP/cmgFSBoSdg6wp77hSXXy5iXEGrncJ/55auDMDaQgQYfa mSkn+7lc93+nszjLG9E6yhuzeuje4pZnOz8iOdq1N1/PuIzw/Vc3Kk/k2Uf4IfHqmZnh DrG97sRzCE4vB2xZh/upois/RxCVuaSdtzMt/GeTjXA3ElFIdswSDZYVzvQQub0oASY3 CZ/w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1728375860; x=1728980660; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=olESbharqUZfyxltqb6oCdmjXv8gjlAHAvdOM2Q2nxA=; b=O+sOxm+is0PidOEmUXGUa5TnLUhm4cJoYfac1XALqRCWOEUyIwSO/C+Iod49tCnwti ZUIfCQv+gdjzXP3TrnltvAhWvc+XaSYIQbcp2waGQdMNeauV7rlrySKrxcz6/K6+RHqz sEbEk9L/EryeMFd0+gpnYgwTFajuiuAy0yk/kRk3fk9wTz15nc1M7eQmzt+nWVzYh83B 6cdgALfdbjHTvIANdQbiEIbEAwelyJbkzfQAQ6timgGTShLFIu/MWMcM+P+2/V8jMTYV 6Hd3i4/aKGnEoqeApkIJtdIUpUHCnIuAVrNDUPsM8qJgFq4CK6nbgbNSeMbBglIwdgaV F9EQ== X-Gm-Message-State: AOJu0YzQymTECd3/DjZA+pBe6a5s/KRynrJJkM9bM+9r8B3RRF+bDq2+ 9zz0e+1Gzg97j648OtwwZb45iqSPxh62L8zCsb8ot+wjnL0OQuupFfKZ67y+267+JzrC+uiMhPl xzvvdmsnMbNCfiwWsar2AD4GlI6KLOy+b X-Google-Smtp-Source: AGHT+IGq+KgUoVRd232Wh0TIle6tKJC/h1oAZ2Ok39sQ9tqoVG3pw4S/DsFm05jtpXT2bWaGnvP7bhr6plhIG3SijCM= X-Received: by 2002:a17:906:f5a9:b0:a99:5f45:cb66 with SMTP id a640c23a62f3a-a995f45cf5fmr184913266b.11.1728375860016; Tue, 08 Oct 2024 01:24:20 -0700 (PDT) MIME-Version: 1.0 From: Sameer Malve Date: Tue, 8 Oct 2024 13:54:11 +0530 Message-ID: Subject: RHEL certified repo provided PostgreSQL Major Version Upgrade. To: pgsql-admin@lists.postgresql.org Cc: Sameer.Malve@mobileum.com Content-Type: multipart/alternative; boundary="0000000000002cbf4d0623f2dd37" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000002cbf4d0623f2dd37 Content-Type: text/plain; charset="UTF-8" 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 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 --0000000000002cbf4d0623f2dd37 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Team,

We are trying to perform the M= ajor 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 faci= ng the below issue.

As the binaries are getting up= graded in-place `/usr/bin` hence=C2=A0while performing pg_upgrade we are no= t getting the older binaries.

pg_upgrade command i= s as follows.

[2024-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-1= 0-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:19] = =C2=A0Please use the -b command-line option or the PGBINOLD environment var= iable.
[2024-10-04 11:19:19] =C2=A0Failure, exiting
=C2=A0

Regards,
Sameer Malve
--0000000000002cbf4d0623f2dd37--