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 1tD5Q6-00FnTD-4D for pgsql-admin@arkaria.postgresql.org; Mon, 18 Nov 2024 17:20:14 +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 1tD5Q4-0068lg-AA for pgsql-admin@arkaria.postgresql.org; Mon, 18 Nov 2024 17:20:12 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tD5Q3-0068lX-UZ for pgsql-admin@lists.postgresql.org; Mon, 18 Nov 2024 17:20:12 +0000 Received: from mail-pj1-x1034.google.com ([2607:f8b0:4864:20::1034]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tD5Q2-002YZu-0G for pgsql-admin@lists.postgresql.org; Mon, 18 Nov 2024 17:20:11 +0000 Received: by mail-pj1-x1034.google.com with SMTP id 98e67ed59e1d1-2ea5a22d80cso1048034a91.0 for ; Mon, 18 Nov 2024 09:20:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1731950409; x=1732555209; 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=BlBEorlBvfJmvPFebI2s4Re7cBHLJurReGm9DiRzsUg=; b=feZbdDxR9D/iVLz9p0IAn7pAs2kYxezheD1MmV/QSiajpwR3I8Jl1t413ZKwNyf6fz PevVMHZ5HcTCSvHi4+FfiLYNRPi29PW5nJCCfA2dE2dAASv3YcKGhZnqI9BOCkFwMfcA xLwbJmGC8OmzdRmmchibK+ncbEvd43/KRGsJY1h5Dp6wKMNkFbaZqnetsI7veiCQtP+e 091cWxWjDnKUjqqJxnIrAniu6JfopvF44lUHVJyzEna/o5c0NB0F7wm7z1ImaIV0YIw1 BemMtS9LZbZPFOKBrm0WYl/p1FL5GswizFoZCd1FawLXPZJT/Y9Gr9lETM/KbL7Svv+N Xh0w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731950409; x=1732555209; 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=BlBEorlBvfJmvPFebI2s4Re7cBHLJurReGm9DiRzsUg=; b=VPHuYNFEjwxvSO3PEjcBOxMaCHcoKg3R8FYBrb4bk0dTG7WBf5FplXucUi7JCmFe/0 dhsAOyh4n82O0fYPWIhd6nSjg+Ng5nRWC/1iCz1V0lSf1hXisz2hveJrNUr7Nvy5v3M4 Net4qAY49vjAj0x0uL4ujgAEDI9pWsD9ix7XgdYf6zDpU0OexXKGKiF6MsebSYMGv1RS x1KBXRy82d3bC5uQAovTWGk3CEcpXsAFAhxgL6QE8NvPwvYQIQCzgyJj60L3q2O2AU4g yTBqQflO3Ju97uI2xtyOncFiOXRz0jFNJXBBCnFI6f8bUUfpV1T0t/Vk86dGbeoYO365 ERvw== X-Gm-Message-State: AOJu0YycPvyNZab2INKlD2Pu7d97N4eZf1VpgnptcUWIiI2jntbt+Z9y UMgCQ1HyBhd//brsCJqD5u5vfDCPpBZ4nMMMp45LF+hLGECxjKmQfq4tvIj/zp+x8MxLJTnqM5e 8PTASEJ9LoamyfGcgW+V7gFr0Pdw= X-Google-Smtp-Source: AGHT+IEWRhFWyztqr/XMrWGC/6D55VEtHfVj4lvWGf+2YejtG6Z6pkgKR0NnG72K4fUQBmPFssIBMJiGCFY4p7Nh9lc= X-Received: by 2002:a17:90b:38c8:b0:2ea:aa69:1069 with SMTP id 98e67ed59e1d1-2eaaa691151mr189293a91.0.1731950408899; Mon, 18 Nov 2024 09:20:08 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Motog Plus Date: Mon, 18 Nov 2024 22:49:54 +0530 Message-ID: Subject: Re: Guidance Needed for PostgreSQL Upgrade from 12 to 15 To: Ron Johnson Cc: Pgsql-admin Content-Type: multipart/alternative; boundary="000000000000e4442d0627332020" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000e4442d0627332020 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 the standby, once upgrade completes on primary? Any suggestions on this please. 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 followin= g: >> >> 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 bot= h >> 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! > --000000000000e4442d0627332020 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks Ron for your suggestion.
So = for pg upgrade in streaming replication setup, rsync will be a better optio= n for standby upgrade if we are using --link option or recreating the stand= by, once upgrade completes on primary? Any suggestions on this please.

Best Regards,
Raman


On Mon, Nov 18, 2024, 22:41 Ron Johnson <ronljohnsonjr@gmail.com> wrote:
On Mon= , Nov 18, 2024 at 11:08=E2=80=AFAM Motog Plus <mplus7535@gmail.com&= gt; wrote:
Dear Team,
<= div dir=3D"auto">
We are in the process of upgra= ding our PostgreSQL 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_upgrade command, from disk space point of view?

Yes.
=C2=A0
Are there an= y potential downsides to consider?

<= div>Very much: it's a one-way journey.=C2=A0 No rolling back if somethi= ng goes=C2=A0wrong!
=C2=A0
2. Do you have any sug= gestions or best practices for performing an efficient upgrade in a replica= tion 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 o= f upgrading PG on one server to PG on a different server.
=C2=A0<= /div>
--
Death to <Redacted>,= and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
--000000000000e4442d0627332020--