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.96) (envelope-from ) id 1w2E7i-0006Q2-29 for pgsql-admin@arkaria.postgresql.org; Mon, 16 Mar 2026 20:01:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w2E7f-00CYeW-21 for pgsql-admin@arkaria.postgresql.org; Mon, 16 Mar 2026 20:01:08 +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.96) (envelope-from ) id 1w2E7f-00CYeI-0S for pgsql-admin@lists.postgresql.org; Mon, 16 Mar 2026 20:01:08 +0000 Received: from mail-oo1-xc2a.google.com ([2607:f8b0:4864:20::c2a]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1w2E7d-00000000TuC-0J4C for pgsql-admin@lists.postgresql.org; Mon, 16 Mar 2026 20:01:07 +0000 Received: by mail-oo1-xc2a.google.com with SMTP id 006d021491bc7-67bad873c3eso3124367eaf.3 for ; Mon, 16 Mar 2026 13:01:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1773691263; cv=none; d=google.com; s=arc-20240605; b=jZnU85L39S6zPkm+0q6gD2rjiX1OoOZPTrzLkrrZtPabX7F8P5aa59WksZ1lBwNFvx mr6jTSxlQXMWMnE/CVDKM3n7bKeiw4ZnJWemqCuFEKbcNpvbdM6ius+xsy9UB1izCegb wg77HNqzYu2DzOz1brbQ7nIsW8kDyzdoQMNQe3gDZplx6G2ss4LasWrMoIuWBpWD26yX h+BEqnDUobHZnvD2W+CYVf3IB+3cr++YTRvSMnjJK3LymXcPLUWjoSoKAtqQfHusIo/x nRztnIlObuoHN5YoKP1s5K++2LaOBxX0OUHxQURqp06drOhdyex35nIB/gx97YBEBYU8 nQ8w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=LDVy7VQUaOQ7LVDfVhLgnTenKQB3xRo40v7teK3lqnU=; fh=druxZHa2fk4e6MLibibygn9AWWgeaAPo4m8Gpo2MBXU=; b=NQTVYg74gXMdQlJ3EVJtPFedZM21VJfkU2sUv+YjNehNGq+Q7J6NemvwkkFDFe5upC DFfFI/oReYPGGeDowMmMIFQUA4z4BLjAwtncpdY/ooMCuk54H9I7IsUKw3QzCdhdBH7Q GmA0O0K9afRCVUfPLpoE+kF0NekrN0+zjD5AwkNOj83UWdJSrWqnnFNTlWJI9N5BVHdw mwr89dWkG5MLW1JpHLu9Pf2bjcNGlC2jg9rSlkiRt7KRVi1VqtK1RJSsmEgfDl6op33w AlFqACqAI5d8AIPb1r+FurM1tumju9CV1zhzdgtNMt0/cUSalBvJXPwiUFsTc0BdGikn h+6A==; darn=lists.postgresql.org ARC-Authentication-Results: i=1; mx.google.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1773691263; x=1774296063; 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=LDVy7VQUaOQ7LVDfVhLgnTenKQB3xRo40v7teK3lqnU=; b=HwPLKkGMiUSa+cixnNGMgrSuxjVCUr055jyHdMgte/6qbyGExq3YSkH6l7Z4Uk1o7k PU6zFYEpPyb0A8BMpouix96Od6XYsTxY02XYqBrieVIjlGXlBjzUzNbH85g+zVoInKG2 Fb9WaaAyT85dO5TIwYevZcAi49qfqJsUvX19hIbowdHPqCUHFZTZB3kMHyUfX+qdl6RP 1ETJYf+KqVxiaXV9nQvkALSyiH/0alg/zqKpEwAy1/pKw2lFbB2/7I/qRS/zYSgcZm+Y Nxc5Pl1gDzFlx2sbuVHiZWvzPjVsc58fNavEIsa6LkiVhe0KxpA/hN8YNJGRQjhToydl icVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1773691263; x=1774296063; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=LDVy7VQUaOQ7LVDfVhLgnTenKQB3xRo40v7teK3lqnU=; b=r/AoUHAJksyffn8x50fnXDdWwZMMQadMg0za2EKL+8/Adx7UKceGsJlpNJ1OcvMyU1 8oqKApewceyJ8hP4L/c897lMYsWHymQw9u0g6mKzLUKtV22RAGQqsnji/3nIBQ7IE7Rw dzf5cpCzWKUlupO+l7CdBhFyLXqJD1ggHB1oT4AYQPhMTucZcI8/cL57bRqY/NakeqWt VvpC+6bPbHb07r225Svx6mBLMVaFzgMLwulxQQpc3XGnJWggFIK9IumpQ4f8IXRRavgi WLr6KLkqvp2NZakgWokE5pbBkPr99H/fRElHXskAnWb1HBYsHfxgM/8ykqASflJYoAaC zFRw== X-Gm-Message-State: AOJu0Yw+/wqLQC/JFWHOLL09KIqOoCwJ6BBsmXvTtLtq4DLBGLsOSben yvrmzL1I3fCAcZqnszID0PPMSAXPnof63LVUVE7itzO3iIzfryp6Fl1dMbaO2vIvBPWV/qcH2D1 PxTT1NiLXclFb5Gfpfehua4doeIGCLDZfamr1 X-Gm-Gg: ATEYQzxsYDjxjpYI/CaC+X0FTkcMGKRPgNG9OAcuh1/puoHiguL7FpDrw9mQUMr1fqS 8fsTSkbzTlW4jb4h8yJ9IXGyEYS6KGzS4n7dn/5N5arA4EhII/C7UpB9gcnK3mkLmT1zHn2XEaO zh4Rwnnim3+mjgrdQJas/v7Q6eac6DmedMyb++WP7b7RSIX3rMC5Bf0dlPaZfmF6DbmCETdIM+C TeeeucXmQR3xC1+3d1iMMINPIGt6n7rPjWNccZ2k5Nf/CdlbwtPyQrvbM3+7l6b3fRbcRe67Gke EHXFCGAe X-Received: by 2002:a4a:ec44:0:b0:679:dcdf:1a0f with SMTP id 006d021491bc7-67bdaa92ce2mr8594267eaf.72.1773691262705; Mon, 16 Mar 2026 13:01:02 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Mon, 16 Mar 2026 16:00:49 -0400 X-Gm-Features: AaiRm51SGlICvoatEtPbba8YyP-53sp92D6LPNvI9kmBJ7pN2i34_fL5e9DvRRg Message-ID: Subject: Re: OS upgrade on postgres servers To: Pgsql-admin Content-Type: multipart/alternative; boundary="000000000000a7a5f7064d29adfa" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000a7a5f7064d29adfa Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Mar 16, 2026 at 3:45=E2=80=AFPM Raj w= rote: > Pgdg repo > 100Gb > That's relatively small. Parallel pg_dump/pg_restore should be pretty fast= . > Outage window - our decision. Client will accept our plan. > Postgres upgrade may or may not be needed. Need help on both the scenario= s > What version of PG are you currently using? (Everything older than PG 14 is EOL, and PG 14 will go EOL this November.) I strongly recommend that you add the PGDG repository to yum/dnf, and then install the intended version (both before and after the upgrade to RHEL10. PG 17.latest or PG 18.latest are best, but of course you need to read the release notes and test your application against that new version. Then, for example: /usr/pgsql-17/bin/pg_dump -Fd -jX .... /usr/pgsql-17/bin/pg_restore -Fd -jX > > On Tue, 17 Mar 2026, 00:41 Ron Johnson, wrote: > >> On Mon, Mar 16, 2026 at 2:57=E2=80=AFPM Raj wrote: >> >>> Hi all, >>> >>> I have traditional servers with postgres with replication setup (primar= y >>> - standby). OS team want to upgrade from rhel 8.10 to 10. >>> >>> As a dba, what is the suggestion we need to give. How do we proceed ? >>> Should we stop the posygres servers? Should we get new servers with rhe= l 10 >>> and migrate Data? >>> >> >> That's certainly a safe method. >> >> >>> What's the best procedure >>> >> >> The main problem is collation change driven by the newer glibc version. >> >> 1. How did you install PG (from the RHEL repository, or from the PGDG >> repository)? >> 2. How big are your databases? >> 3. How big is your outage window? >> 4. Do you plan on upgrading Postgresql at the same time? >> > --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --000000000000a7a5f7064d29adfa Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Mon, Mar 16,= 2026 at 3:45=E2=80=AFPM Raj <rajeshkumar.dba09@gmail.com> wrote:
Pgdg repo
100Gb

That's = relatively small.=C2=A0 Parallel pg_dump/pg_restore should be pretty fast.<= /div>
=C2=A0
Outage window - our decision. Client will = accept our plan.
Postgres upgrade may or may not be = needed. Need help on both the scenarios=C2=A0
<= div>
What version of PG are you currently using?=C2=A0 (Every= thing older than PG 14 is EOL, and PG 14 will go EOL this November.)
<= div>
I strongly recommend=C2=A0that you add the PGDG reposito= ry to yum/dnf, and then install the intended version (both before and after= the upgrade to RHEL10.

PG 17.latest or PG 18.late= st are best, but of course you need to read the release notes and test your= application against that new version.

Then, for e= xample:
/usr/pgsql-17/bin/pg_dump -Fd -jX ....
<upgr= ade RHEL to v10>
/usr/pgsql-17/bin/pg_restore -Fd -jX
=C2=A0

On Tue, 17 Mar 2026, 00:41 Ron Johnson, <= ;ronljohnsonjr= @gmail.com> wrote:
On Mon, Mar 16, 2026 at 2:57= =E2=80=AFPM Raj <rajeshkumar.dba09@gmail.com> wrote:
Hi all,

= I have traditional servers with postgres with replication setup (primary - = standby). OS team want to upgrade from rhel 8.10 to 10.

As a dba, what is the suggestion we need to= give.=C2=A0 How do we proceed ? Should we stop the posygres servers? Shoul= d we get new servers with rhel 10 and migrate Data?

That's certainly a safe method.
=C2=A0
What's the best procedure

The main problem is co= llation change driven by the newer glibc version.

= 1. How did you install PG (from the RHEL repository, or from the PGDG repos= itory)?
2. How big are your databases?
3. How big is yo= ur outage window?
4. Do you plan on upgrading Postgresql at the= =C2=A0same time?
=C2=A0

-= -
De= ath to <Redacted>, and butter sauce.
Don't boil me, I'm s= till alive.
<Redacted> lobster!
<= /div>
--000000000000a7a5f7064d29adfa--