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 1tIqd5-00H2Tf-Kb for pgsql-admin@arkaria.postgresql.org; Wed, 04 Dec 2024 14:45:27 +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 1tIqd2-000Fw5-7Y for pgsql-admin@arkaria.postgresql.org; Wed, 04 Dec 2024 14:45:25 +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 1tIqd1-000Fvw-Sa for pgsql-admin@lists.postgresql.org; Wed, 04 Dec 2024 14:45:25 +0000 Received: from mail-oi1-x22a.google.com ([2607:f8b0:4864:20::22a]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tIqd0-0011jF-CG for pgsql-admin@lists.postgresql.org; Wed, 04 Dec 2024 14:45:24 +0000 Received: by mail-oi1-x22a.google.com with SMTP id 5614622812f47-3ea552bb91aso435377b6e.1 for ; Wed, 04 Dec 2024 06:45:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1733323521; x=1733928321; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=xv55Vd8sPsPzwPfUFISXoOX+NaGNIKrKbnNdSaPvVWY=; b=dnwz3uG0lReJ7bg8AIHsJIhfjHxADp+57ctK0Ft6gAtwlqZa2mEQY0INqubKbECbgL o+wCRoEMRfyg2h8EUYQk/TnkwTbQi8TIHiCsdqTINFPd6jjCUeeecf1rZLzak/iNi/RS 3mTUNkIkVewq2xRSF+NG5vBQXufL/0ADA2NwsIa8I5Vo0IqErdoUex9S3nTjg4F6J2WO Qz98HiRIHRfR9wAx2ciDuSR3PHaI8nYJm593gt2gDpdPoHXT1mRiYhVozTDuwHDZKrel Hq9yvgtRpEVzx9JyyWduqsi/mFjrFytA6DUYzlb004tKW5Hd2T8LrDkXHgxmC1nftJeW kEUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1733323521; x=1733928321; h=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=xv55Vd8sPsPzwPfUFISXoOX+NaGNIKrKbnNdSaPvVWY=; b=c8t0U+Qf98Ru0D69VGaOV2Zt8FPVt4lGUA9CRgpd5pvheYelT/SdZdt+WX0AzT4bJb yva//uy/lrUKQFEXsyOlJeSGQK3mmz0hxAOO3c+LeIjgMdNRwwIJWdG0KUxB8ZmuynMs ztLwmJd1xTuUvGeT/vWVQyGWIDmtEtu+xSWMOku8VOmRX0WLvggoGkXzuHFAOvLXYxfo w4nK0sXHlusu40mpXVr1O4OOGwS7TBEFKTPIbhnH89N0vfsOK38C5xhhbsC0e7OZ7wzW jAsgo7zljJvj69Iqba+fjCwW67M/mUPqmDDSkRNkvw5mgOLQFN73rU/DCVfCYmn32g06 2BgQ== X-Gm-Message-State: AOJu0YwODUPzozuTPoAZAbbHusK+5Kupmo3cCYhLRHnPt/dKe3jP+Tdt al0TJ1/3AStd9/he+rcO2wDUw7RMDG/mA7ZgOPhxKy6fyuZT92A1nr8mZQmPiLP5hHbkGItM6su RNNGFKv955UOv7URgFCMXj3iH+G+rEQ== X-Gm-Gg: ASbGncttFlt5hLH3bJk4nDoPwoRjgWR5xyuQTQaGc0+E7LjIM8j2emosZubhjCaCWSt 3ox5B4PZIGVIpw9YB3p44IBeVbQMhwSlfr05JwUzVuCXttP5OGvh1uhsGOagXBi4Mkw== X-Google-Smtp-Source: AGHT+IHufHCBHv0+lRGYC/oskb3jJzg/VMQy4nb3ceIR/g3Qvnx5LtN4zXsrKawV0MKoq/yL0+8c7w1JRgK/x+uiiOc= X-Received: by 2002:a05:6808:10cd:b0:3e0:3f2e:3d86 with SMTP id 5614622812f47-3ea814ed76amr18423298b6e.8.1733323519190; Wed, 04 Dec 2024 06:45:19 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Wed, 4 Dec 2024 09:45:07 -0500 Message-ID: Subject: Re: Postgres compatibility with RHEL To: Pgsql-admin Content-Type: multipart/alternative; boundary="000000000000a46dba062872d417" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000a46dba062872d417 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Dec 4, 2024 at 8:03=E2=80=AFAM Siddhartha Jain wrote: > Hi, > > Please let me know if Postgresql 16 is compatible with RHEL 7.9 version > and RHEL 9.1 version. > I need to upgrade postgres from 11.22 to 16.6 and need information for > that as the OS version is going to upgrade from 7.9 to 9.1. > Also, let me know the strategies if any to upgrade both RHEL and DB. > Are you doing an in-place RHEL upgrade on the server? If so, then I'd: 1) run pg_dump, "pg_dumpall -g", and save postgresql.conf, pg_hba.conf, etc files when the server is still RHEL 7.9 and PG 11.22, 2) upgrade to RHEL 9.1 (out of scope for this list), 3) install PG 16.6, 4) what you do next depends on your mount points. --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --000000000000a46dba062872d417 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Dec 4, 2024 at 8:03=E2=80=AFAM Si= ddhartha Jain <siddharthaj= ain92@gmail.com> wrote:
Hi,

Please let me know if Postgresql 16 is compat= ible with RHEL 7.9 version and RHEL 9.1 version.
I n= eed to upgrade postgres from 11.22 to 16.6 and need information for that as= the OS version is going to upgrade from 7.9 to 9.1.=C2=A0
Also, let me know the strategies if any to upgrade both RHEL and DB.= =C2=A0

Are you doing an in-plac= e RHEL upgrade on the server?=C2=A0 If so, then I'd:
1) run p= g_dump,=C2=A0"pg_dumpall -g", and save postgresql.conf, pg_hba.co= nf, etc files when the server is still RHEL 7.9 and PG 11.22,=C2=A0
2) upgrade to RHEL 9.1 (out of scope for this list),=C2=A0
3) = install PG 16.6,
4) what you do next depends on your mount points= .

--
Death to = <Redacted>, and butter sauce.
Don't boil me, I'm still al= ive.
<Redacted> lobster!
--000000000000a46dba062872d417--