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 1sy8H9-00EaRs-FS for pgsql-admin@arkaria.postgresql.org; Tue, 08 Oct 2024 11:21:11 +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 1sy8H8-007SYG-6m for pgsql-admin@arkaria.postgresql.org; Tue, 08 Oct 2024 11:21:10 +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 1sy8H7-007SY1-R6 for pgsql-admin@lists.postgresql.org; Tue, 08 Oct 2024 11:21:09 +0000 Received: from mail-ej1-x633.google.com ([2a00:1450:4864:20::633]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sy8H6-003BSI-DJ for pgsql-admin@lists.postgresql.org; Tue, 08 Oct 2024 11:21:09 +0000 Received: by mail-ej1-x633.google.com with SMTP id a640c23a62f3a-a99409f1cc7so16628066b.2 for ; Tue, 08 Oct 2024 04:21:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1728386467; x=1728991267; 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=kcz1buKaAFmgBvs7Wciig4imofHwNIvw/Q7/thIqpY0=; b=lGv7vt17S4gSz8yqNbZZnLBqE86k4WhflzxYEAca8NF8kjd9DqoidWFMK+IkAUSMfa jB/KGDVmiRaMnBmQeQ1vdQqRN4zsnuJBhm8188CwZdGOUNxfItLg8q791Y4wx3DdOr4q TGNY9VxuAdfKdh0UACQsfIaRHeQZvNC0vQfTr1YV8hxX8bHO7qYq4scTVnlvcNqqJtmk HnQey0fEWxq+OsKtZwQi46ibEuT+AWkQgEP8THRNc+VU39wn94pMOLWfc361H8oPtM0A /n65x6sOxju5v1+26KNmCp+plujXLeV4E+xyTuqPyk5Elj5mjafU3KPg+HczGspm8n6w Uqjg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1728386467; x=1728991267; 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=kcz1buKaAFmgBvs7Wciig4imofHwNIvw/Q7/thIqpY0=; b=ODcMNSZFo7u0NbqL2P7pzJcQ/PWYDwnoz7Iq4fBfpAkjqkGjoEFTj5N8cjO2Nr+M0l qboSBFHv+k8C3kjkPVgKfVjpSbOdO/wMCJDYsSn8eC70iCsqckyLDTEr8i8ODYDLAkAe XYCGUEgR0IZk8iQ5PwSXqNirX0/PVhC5yF4iJMoBr2E9nIlwneh2Q19Z+Mi1ziOnGmeb k16HQa0UNxlK8SSD2xeiTC6IIQeGjDFZJrY9S29H24pT+bN141Iw322cMzCOLtt7A0SQ d5uttl2J2vhzcAT8+9/a8OF4Ekka+s52A/919tUyp+KnRhMu3b7y6sXp2SzHdB9geGdd 5RMQ== X-Forwarded-Encrypted: i=1; AJvYcCXMgJD49M7+gUKvzdYUgT2yIzqCQNgy2cu6IZjBGXdwrCtMsUuHJW/S0URLYfit4uEvffOVC20bZUpqOA==@lists.postgresql.org X-Gm-Message-State: AOJu0Yw+iwP/Hi9/lZPwlI352zPM3RZFH2LKHKLbRMk+vxwpgGRW/JRk r/+ZH5mX42wNPWUNDzDcc7e6L99xV27pC1zqi3CmpUeGYxmGg2ccOz2cTmeKl5TB/3Z968aSlwG 0tmOVDBjn3dWSlBY7I+qq64Oilcc= X-Google-Smtp-Source: AGHT+IHzzADYPpfKkR3qWdCaayCMnUevP9lOtObWx4Y9TJeAHKgINSxdTqso+OoczI8jfw3dI7Kxx/L+bXpqPxgaKLo= X-Received: by 2002:a17:906:794e:b0:a99:8034:b213 with SMTP id a640c23a62f3a-a998034b954mr20118966b.4.1728386467345; Tue, 08 Oct 2024 04:21:07 -0700 (PDT) MIME-Version: 1.0 References: <5e25f0ae351c9be37078c9d75cbbfd3993527b4c.camel@cybertec.at> In-Reply-To: <5e25f0ae351c9be37078c9d75cbbfd3993527b4c.camel@cybertec.at> From: Sameer Malve Date: Tue, 8 Oct 2024 16:50:58 +0530 Message-ID: Subject: Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. To: Laurenz Albe Cc: Zaid Shabbir , pgsql-admin@lists.postgresql.org, Sameer.Malve@mobileum.com, purav.chovatia@mobileum.com Content-Type: multipart/alternative; boundary="0000000000006bc1970623f55553" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000006bc1970623f55553 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable +purav.chovatia@mobileum.com Hi Laurenz , We have installed the PostgreSQL from RHEL repo using `dnf install ` so we have not passed any customised path for installation. And there the problem arises as older version binaries get overwritten when we upgrade/ install the new version of Postgres. Regards, Sameer Malve On Tue, Oct 8, 2024 at 4:18=E2=80=AFPM Laurenz Albe wrote: > On Tue, 2024-10-08 at 16:03 +0530, Sameer Malve wrote: > [about pg_upgrade] > > Does this Upgrade command stand true in case of postgres upgrade betwee= n > community (PGDG) to RHEL? > > Probably, unless they configured something differently that affects > the storage format. Try and see. > > Recommendation: keep using PGDG packages. > > Yours, > Laurenz Albe > --0000000000006bc1970623f55553 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
+purav.chovatia@mob= ileum.com=C2=A0

Hi = Laurenz ,

We have installed the PostgreSQL from RH= EL repo using `dnf install <package name>` so we have not passed any = customised path for installation.

And there the pr= oblem arises as older version binaries=C2=A0get overwritten when we upgrade= / install the new version of Postgres.=C2=A0=C2=A0

Regards,
Sameer Malve

<= div class=3D"gmail_quote">
On Tue, Oct= 8, 2024 at 4:18=E2=80=AFPM Laurenz Albe <laurenz.albe@cybertec.at> wrote:
On Tue, 2024-10-08 at 16:03 +0530, Sa= meer Malve wrote:
[about pg_upgrade]
> Does this Upgrade command stand true in case of postgres upgrade betwe= en community (PGDG) to RHEL?

Probably, unless they configured something differently that affects
the storage format.=C2=A0 Try and see.

Recommendation: keep using PGDG packages.

Yours,
Laurenz Albe
--0000000000006bc1970623f55553--