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 1tD5WD-00FoNi-VG for pgsql-admin@arkaria.postgresql.org; Mon, 18 Nov 2024 17:26:34 +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 1tD5WB-006FoN-K8 for pgsql-admin@arkaria.postgresql.org; Mon, 18 Nov 2024 17:26:32 +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 1tD5WB-006FoE-7B for pgsql-admin@lists.postgresql.org; Mon, 18 Nov 2024 17:26:31 +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 1tD5W5-002bja-IG for pgsql-admin@lists.postgresql.org; Mon, 18 Nov 2024 17:26:31 +0000 Received: by mail-ot1-x32d.google.com with SMTP id 46e09a7af769-71806621d42so1481521a34.3 for ; Mon, 18 Nov 2024 09:26:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1731950783; x=1732555583; 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=pmks7sgWs4WOU0KZ/qkq9UkjnuC8nnviEZxgE4erA7M=; b=RinEfOy80JfjJTvjqTznvI/SwB7ZtgR4QCXoBx2iLZE1EqutMT6PKVsXAORPgYHclK pa0iK00B8KOLDQ9l36qp/p+K1eVcAzARHWbTdXmFfunBef1K8SSv6nVID7mkIbfN68s8 on3w8hfU9z0gslk1qdjpnTCboKbHYMsRAC13Ho4Zdz1GGvasUq7jSZ7Tr2lvBRPwIz/w J26SYPMNQOsCukyrNFKH2aKxgoMCWVPq3tSIsQXwnDKmcm+Z7TOFNm/AXU4fBJ0YCoGt s5Kxhj8M0qcCiMKMQJpspFlv9cJGA3d3XF7V5DNbJuEMDpAAiLo280hWcOw8jfLLntOr vkYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731950783; x=1732555583; 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=pmks7sgWs4WOU0KZ/qkq9UkjnuC8nnviEZxgE4erA7M=; b=DBVIQv4aoz4TiFgufaIEU2+EopFTlLYNbYk2uzOlJVqvsRsjAqC82Elro66Y5cOQX2 BE7HhOMtr2f5fXjfXsTZsNzfh40398TX0rRuv/hhupFKaSrRc4wBYLuKz+Bl3LfiT2vn hTz0Fe8hnxdeLPTy71vEJ02EUHF+dTocsK460TJwaKXd0k9EZx4zV2tSsNE2pN9O6IFc XeauPydaoLyV0V6aHvuO9hE5OIx3n2D9qTpkxa5XDeNHeuZ1YdeuM4RiHUCDxPcq8bD0 UJRBhc/SErya+M0T3l1f89evYRB3tJRhebXWXEMle6FtgbA9/AykxZfRpy9DCgfeQaBm 1Gww== X-Gm-Message-State: AOJu0Yw4zKbEZqp080JPwkGdZTlmof7LHQF2Hk36hPukZkfkilm0jCW2 YWKzMVGwe9grpv/IVfxHcNB6eE5QVQYoS6dM2Z2+jDpuTe5TuN5/rYKxfv3bYg13UfojkfRddvB PNyXKLIwLlcpSLVapEMp5+uR3LUwoBg== X-Google-Smtp-Source: AGHT+IGPKV6Tyqe+bfuv5M4+RwUVPpPUZuYSwgt6mQfXbs1XmA3rfOXQgZhtzdRXuYKDgxn/Th5jCT8SghxgHbUhR80= X-Received: by 2002:a05:6830:3692:b0:718:1109:9628 with SMTP id 46e09a7af769-71a77937564mr11995087a34.5.1731950783224; Mon, 18 Nov 2024 09:26:23 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Mon, 18 Nov 2024 12:26:12 -0500 Message-ID: Subject: Re: Guidance Needed for PostgreSQL Upgrade from 12 to 15 To: Pgsql-admin Content-Type: multipart/alternative; boundary="00000000000033e3f806273337b3" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000033e3f806273337b3 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable No. Neither rsync nor streaming replication will do version upgrades. The only ways to do version upgrade are: 1. pg_dump + pg_restore 2. pg_upgrade 3. Logical replication On Mon, Nov 18, 2024 at 12:20=E2=80=AFPM Motog Plus w= rote: > Thanks Ron for your suggestion. > So for pg upgrade in streaming replication setup, rsync will be a better > option for standby upgrade if we are using --link option or recreating th= e > standby, once upgrade completes on primary? Any suggestions on this pleas= e. > > Best Regards, > Raman > > > On Mon, Nov 18, 2024, 22:41 Ron Johnson wrote: > >> On Mon, Nov 18, 2024 at 11:08=E2=80=AFAM Motog Plus wrote: >> >>> Dear Team, >>> >>> We are in the process of upgrading our PostgreSQL database from version >>> 12 to version 15. I would greatly appreciate your advice on the followi= ng: >>> >>> 1. Would it be recommended to use the --link option with the pg_upgrade >>> command, from disk space point of view? >>> >> >> Yes. >> >> >>> Are there any potential downsides to consider? >>> >> >> Very much: it's a one-way journey. No rolling back if something >> goes wrong! >> >> >>> 2. Do you have any suggestions or best practices for performing an >>> efficient upgrade in a replication setup (streaming replication) for bo= th >>> the primary and standby servers? >>> >> >> Streaming replication is not an upgrade method. Logical replication is >> absolutely a valid method of upgrading PG on one server to PG on a >> different server. >> >> -- >> Death to , and butter sauce. >> Don't boil me, I'm still alive. >> lobster! >> > --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --00000000000033e3f806273337b3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
No.=C2=A0 =C2=A0Neither rsync nor streami= ng replication will do version upgrades.

The only ways to do version upgrade are:
1. pg_dump=C2=A0+ pg_= restore
2. pg_upgrade
3. Logical replication

<= div class=3D"gmail_quote">
On Mon, Nov= 18, 2024 at 12:20=E2=80=AFPM Motog Plus <mplus7535@gmail.com> wrote:
Thanks Ron for your sugg= estion.
So for pg upgrade in streaming replication setup, = rsync will be a better option for standby upgrade if we are using --link op= tion or recreating the standby, once upgrade completes on primary? Any sugg= estions on this please.

= Best Regards,
Raman


On Mon, Nov 18, 2024, 22:41 R= on Johnson <ronljohnsonjr@gmail.com> wrote:
On Mon, Nov 18, 2= 024 at 11:08=E2=80=AFAM Motog Plus <mplus7535@gmail.com> wrote:<= br>
Dear Team,

We are in the process of upgrading our Po= stgreSQL database from version 12 to version 15. I would greatly appreciate= your advice on the following:

1. Would it be recommended to use the --link option with the pg_upgr= ade command, from disk space point of view?
<= br>
Yes.
=C2=A0
Are there any potential= downsides to consider?

Very mu= ch: it's a one-way journey.=C2=A0 No rolling back if something goes=C2= =A0wrong!
=C2=A0
2. Do you have any suggestions o= r best practices for performing an efficient upgrade in a replication setup= (streaming replication) for both the primary and standby servers?

Streaming replication is not an upgrade= method.=C2=A0 Logical replication is absolutely a valid method of upgradin= g PG on one server to PG on a different server.
=C2=A0
--
Death to <Redacted>, and butte= r sauce.
Don't boil me, I'm still alive.
<Redac= ted> lobster!


--
Death to <Redacted>, and butter sauce.Don't boil me, I'm still alive.
<Redacted> lobs= ter!
--00000000000033e3f806273337b3--