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 1tNYmi-000cFV-JA for pgsql-admin@arkaria.postgresql.org; Tue, 17 Dec 2024 14:42:53 +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 1tNYli-002K4a-B8 for pgsql-admin@arkaria.postgresql.org; Tue, 17 Dec 2024 14:41:50 +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 1tNYlh-002K4S-TD for pgsql-admin@lists.postgresql.org; Tue, 17 Dec 2024 14:41:49 +0000 Received: from mail-ot1-x32d.google.com ([2607:f8b0:4864:20::32d]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tNYle-000CPN-FW for pgsql-admin@lists.postgresql.org; Tue, 17 Dec 2024 14:41:49 +0000 Received: by mail-ot1-x32d.google.com with SMTP id 46e09a7af769-71ded02b779so2727271a34.2 for ; Tue, 17 Dec 2024 06:41:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1734446504; x=1735051304; 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=gk7zzcaPJ0cA5NBj3vTXkhe/F5iVTom708tapPFyjRA=; b=LUaivq56MSo/3TgLHwtDTB6Bkd97oUX7+tSGRhW46il/WRdsflO6K+K6zvxqYE18fL +g+KRrWnL2NgN9Gnbxk4ZVUBGGwU9im8Lb4LHAhXlYvxs3/Dtit/OXKIiJ9veXsJ55P3 5ZFm7cfGSzdALd/k0bjpBcAajOr2y8wc3w9zXddaQrpYF3L5IxLW5Iwu/3RBtBPxIhzD N8hFccdpZwqMaNnUgvoTOYRpj6P2q/8brIi3K8GTIa9e7FdjtaBPnzIP5OLTRqMrNS+/ xqfhVE1PZpnPTCf2tQZxUQVgJIh2JrIrCrbiPOw68Ey1RblN53ymFrfYEdSSCSd3d236 rgLw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734446504; x=1735051304; 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=gk7zzcaPJ0cA5NBj3vTXkhe/F5iVTom708tapPFyjRA=; b=QujRbtWKGxMmq3BrUMYJPr6ApdRui037dN6TFJ2nUU27m6Hcja3bkyHXhmy60y+V+K IvmdiomdKBh6eMc5yPT3PV6xUHR+h2NJHYcI+5dGiyVFkxTXm9ENWTaToWrd9uIpZFV4 Hp7vAhqUYtYRPINddIxYwp1SbtQgzPZDFJmSc+sdjAxXzJeisIPJZLnJyPGSsM3S1ZUF l33b6ioqbPbL71acOLOGsFK9uk/Jb5+p/7M76VlCpe6dvzQiylYv2ksy3LA2vbnmqw/V RPmyFejIzRR5wKmlIUwvFsXPxImOjq7u2zNSQxe4p42WiorWQbx6mxKhLx3CZ45hr7hZ BMPg== X-Gm-Message-State: AOJu0YxrdTOVRl09XGmJ9bn5liRHNesjOxUrS/bet3Y+VMNf4jG0xlur /Wc1kuS4ZRmwm3ItT04f6oJsn/lCUQKG6Xq57jOuu0pSn1FGuw0w3njUvVeaPyl5AZg37T+lFHM US6YSfBlwOGpPcvL7CC8CdFs5wPvvgknQ X-Gm-Gg: ASbGnctpOVHL0XcGoJ+VFvcPukV+qLIs1XuhKbtHAEkTtet1oWn5q6UxpPTsm+DXgV0 ZNS3b/2sV2thGLO3owvfKz/Vw9jx0lhjKmljeOKI= X-Google-Smtp-Source: AGHT+IEQA/jIFQYjLGc1n4MojgPSTYVAGrK6VhVzPZ4N3kab12p4iUktEWlSL+ux90Iva4TP4eHQPx2+oXV+I3ZCHUs= X-Received: by 2002:a05:6830:2b23:b0:71d:e5fe:605d with SMTP id 46e09a7af769-71e3b80fd6cmr9355355a34.2.1734446504304; Tue, 17 Dec 2024 06:41:44 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Tue, 17 Dec 2024 09:41:33 -0500 Message-ID: Subject: Re: Postgres upgradation To: Pgsql-admin Content-Type: multipart/alternative; boundary="000000000000c56a430629784b7e" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000c56a430629784b7e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Dec 17, 2024 at 5:21=E2=80=AFAM Narendran .j wrote: > Hello All, > > In our environment, PostgreSQL is currently running on lower versions, > ranging from 9 to 11. > PG 9.x is presumably running on an EOL version of the OS, meaning you'll migrate to a current version of the OS. That means you'll use pg_dump/pg_restore OR Logical Replication, instead of pg_upgrade. You should probably do the same on the server running PG 11. > We are planning to upgrade to the latest version, and I have a few > questions regarding the process. > > What are the key considerations or checks we need to perform before the > upgrade? > > Can we directly upgrade from version 9 to 15, or is a step-by-step upgrad= e > required? > Read https://www.postgresql.org/docs/current/app-pgdump.html and https://www.postgresql.org/docs/current/app-pgrestore.html > How should we handle extensions during the upgrade process? > Depends on the extension, and how you install Postgresql. Since we install from RPM packages, it was as simple as installing the latest versions of those packages, and then running pg_restore. > What challenges or issues should we anticipate during or after the upgrad= e? > You might need to update db drivers like JDBC at the same time. > If anyone with experience in upgrading Postgres, please share your > guidance. > Since pg_dump can be performed online, test the process beforehand. I'd bet that your app servers are also running on old servers, too. Upgrade them, and you'll have a perfect chance to test the system beforehand. The only hiccup we faced when moving from PG 9.6 to 14 was that the updated JDBC drivers on the application servers choked on some strings with quotes in them. YMMV. --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --000000000000c56a430629784b7e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, Dec 17, 2024 at 5:21=E2=80=AFAM N= arendran .j <jnarendran3@gmail.= com> wrote:
Hello All= ,

In our environment, PostgreS= QL is currently running on lower versions, ranging from 9 to 11.

PG 9.x is presumably running on an EOL version of the OS, mean= ing you'll migrate to a current version of the OS.=C2=A0 That means you= 'll use pg_dump/pg_restore OR Logical Replication, instead of pg_upgrad= e.

You should probably do the same on the server r= unning PG 11.
=C2=A0
We are planning= to upgrade to the latest version, and I have a few questions regarding the= process.

What are the k= ey considerations or checks we need to perform before the upgrade?

Can we directly upgrade from ver= sion 9 to 15, or is a step-by-step upgrade required?



=

Depends on the extension, and how you install Postgresq= l.=C2=A0 Since we install from RPM packages, it was as simple as installing= the latest versions of those packages, and then running pg_restore.
<= div>=C2=A0


--
Death to <Redacte= d>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
--000000000000c56a430629784b7e--