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 1tFFbA-00C7mX-MI for pgsql-general@arkaria.postgresql.org; Sun, 24 Nov 2024 16:36:36 +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 1tFFb8-008MX0-13 for pgsql-general@arkaria.postgresql.org; Sun, 24 Nov 2024 16:36:34 +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 1tFFb7-008MWs-HY for pgsql-general@lists.postgresql.org; Sun, 24 Nov 2024 16:36:33 +0000 Received: from mail-pl1-x634.google.com ([2607:f8b0:4864:20::634]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tFFb0-003Yei-Qn for pgsql-general@postgresql.org; Sun, 24 Nov 2024 16:36:32 +0000 Received: by mail-pl1-x634.google.com with SMTP id d9443c01a7336-21260209c68so34844855ad.0 for ; Sun, 24 Nov 2024 08:36:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1732466186; x=1733070986; darn=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=guIyl1H0ugiU54SJIVgneA/ZjbzV/rhsQBAT2Znj0bk=; b=nR8aAZDI/3Sv3gsrJlLdMSmkC4P6v26qoLEzbyKMoUyk24LrGAw8tn4iJGfpkpcRym d9GhXHj2pL/pKC6hFVkiAQ4DDMCE5OJbZJSu6PvGEsHbxiA0BlyvDwsu28D+Ui4DS/ds maBC1N6DDLw0uQBkV4rAo79xT/fNn34ZHFFLjh8NYJ2vhzRms4Qqg/jDFsI1eekBD3ND pEntjdkLPEWJ/P39uh9v98oJb12aL9wGaUesE5hRAamufpexMusQ3JZ/e2fIWHWseRho ikwM6aqfO9B8Jp/QMGS/l97EnyH1cxTM1pov/od97gELYeE68d7AeyaMCoiYA5fWB2fd 6zvQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732466186; x=1733070986; 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=guIyl1H0ugiU54SJIVgneA/ZjbzV/rhsQBAT2Znj0bk=; b=mTOPA3A1CZcSPmqQonl7/NwGaNwtRIj+vxx7NVXJ8XHwfMhgW6u1X2rrqeJrJnkyG0 GloYjEXDmZjvBl1UXMvemCPWHuV/9551Bk0uX/ZyAy/A8PmeWQB3WyCBT0rxwkhcQbVh E4zfz17COijTgeuM0a0jvszlOTUlwh4pwMWyDvOSmx5MLxkj8Wk4XJ2FKxOQ91+RhphK 6GOK/TcOyl93PGDAjOcYKcJRDxPfMUca+AIsUOSdQwkgF0pJAtB+oFx3OBWYTV+JkwTR HFy9/06FEyHH6+NtNXvNZxKVv1VUNVwRvubm6v7UfRanTsG/zmxQytAaCzJFybPWVF0R aDVQ== X-Gm-Message-State: AOJu0Yw+S+Z2OlA1eLcCuNe1Yiqzy3XhSDFLQWLbqbF0pE6B4/BMrPjD Rp1qh/CnVrj2kRDXqe192x5X1prAoZVFBGDY1eMH90+on7AVCFYDOw5c+EyPYtSMXaFMSWZyMwZ qjWqZChU80cfui0eSrg2eaXhz73E= X-Gm-Gg: ASbGnctJF1YA+zgHV4XzaZa1LzN8x1u1LaRZP94/a3bLFtV/pZ/L7T+Hx6IRKTDkKBB sQeghLPRh/rl1pCOwQgR5fTzFMLEWgw== X-Google-Smtp-Source: AGHT+IHMK6VlfT/9kMK09F4bkYmorjb3gmqN+rXHSrB+8a8qvQMlIr+yWPURgcCEO7SxILsk1098zN/7PrQaGz9Xiko= X-Received: by 2002:a17:903:230e:b0:20b:c043:3873 with SMTP id d9443c01a7336-2129fea837bmr150354805ad.21.1732466185514; Sun, 24 Nov 2024 08:36:25 -0800 (PST) MIME-Version: 1.0 References: <6c498f0e-64f9-449a-9b90-5cd72d00e2ef@aklaver.com> In-Reply-To: <6c498f0e-64f9-449a-9b90-5cd72d00e2ef@aklaver.com> From: Subhash Udata Date: Sun, 24 Nov 2024 22:06:14 +0530 Message-ID: Subject: Re: Questions on Upgrading PostgreSQL from 15.0 to 15.9 and Setting Up Streaming Replication To: Adrian Klaver Cc: pgsql-general@postgresql.org Content-Type: multipart/alternative; boundary="00000000000092b5bf0627ab377c" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000092b5bf0627ab377c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable The reason to upgrade from 15.0 to 15.9 is this https://www.postgresql.org/support/security/CVE-2024-10979/ Here it is mentioned that this vulnerability is fixed in 15.9 So our organization wants an upgrade from 15.0 to 15.9 On Sun, 24 Nov 2024 at 21:48, Adrian Klaver wrote: > On 11/24/24 08:05, Subhash Udata wrote: > > Dear PostgreSQL Community, > > > > I have a production database setup with a primary server and a standby > > server. The database is currently running on *PostgreSQL 15.0*, and I > > plan to upgrade both servers to *15.9*. > > > > I have the following questions regarding the upgrade and replication > > process: > > > > 1. > > > > *Upgrade and Replication Compatibility*: > > > > * My plan is to perform a failover, promote the standby server > > (currently 15.0) to primary, and then upgrade the old primary > > server to version 15.9. > > * After upgrading the old primary server to version 15.9, I want > > to configure it as a standby server and set up streaming > > replication with the new primary server, which will still be > > running version 15.0. > > * Is it possible to establish streaming replication between these > > two versions (*15.0* as primary and *15.9* as standby)? > > 2. > > > > *Efficient Replication Setup*: > > > > * The production database is around *1TB in size*, and creating > > replication using |pg_basebackup| is taking more than 2=E2=80= =933 hours > > to complete. > > * Is there an alternative method to set up replication without > > taking a full backup of the entire cluster but instead using > > only the WAL files that have changed on both servers? > > Why? > > 15.0 --> 15.9(actually you want the latest release 15.10) is a minor > upgrade it involves shutting down the servers installing the new version > binaries on each and restarting them. > > You should read: > > https://www.postgresql.org/support/versioning/ > > It would be a good idea to go through the Release Notes here: > > https://www.postgresql.org/docs/15/release.html > > To see what changed. > > > > > Your guidance and recommendations on these questions will be greatly > > appreciated. > > > > Thank you for your time and support! > > > > Best regards, > > > > Subhash > > > > -- > Adrian Klaver > adrian.klaver@aklaver.com > > --00000000000092b5bf0627ab377c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
The reason to upgrade from 15.0 to 15.9 is this
https://ww= w.postgresql.org/support/security/CVE-2024-10979/

Here it i= s mentioned that this vulnerability is fixed in 15.9
So our organization= wants an upgrade from 15.0 to 15.9

On Sun, 24 Nov 2024 at 21:48, Adri= an Klaver <adrian.klaver@ak= laver.com> wrote:
On 11/24/24 08:05, Subhash Udata wrote:
> Dear PostgreSQL Community,
>
> I have a production database setup with a primary server and a standby=
> server. The database is currently running on *PostgreSQL 15.0*, and I =
> plan to upgrade both servers to *15.9*.
>
> I have the following questions regarding the upgrade and replication <= br> > process:
>
>=C2=A0 1.
>
>=C2=A0 =C2=A0 =C2=A0*Upgrade and Replication Compatibility*:
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0* My plan is to perform a failover, promote = the standby server
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0(currently 15.0) to primary, and then= upgrade the old primary
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0server to version 15.9.
>=C2=A0 =C2=A0 =C2=A0 =C2=A0* After upgrading the old primary server to = version 15.9, I want
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0to configure it as a standby server a= nd set up streaming
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0replication with the new primary serv= er, which will still be
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0running version 15.0.
>=C2=A0 =C2=A0 =C2=A0 =C2=A0* Is it possible to establish streaming repl= ication between these
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0two versions (*15.0* as primary and *= 15.9* as standby)?
>=C2=A0 2.
>
>=C2=A0 =C2=A0 =C2=A0*Efficient Replication Setup*:
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0* The production database is around *1TB in = size*, and creating
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0replication using |pg_basebackup| is = taking more than 2=E2=80=933 hours
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0to complete.
>=C2=A0 =C2=A0 =C2=A0 =C2=A0* Is there an alternative method to set up r= eplication without
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0taking a full backup of the entire cl= uster but instead using
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0only the WAL files that have changed = on both servers?

Why?

15.0 --> 15.9(actually you want the latest release 15.10) is a minor upgrade it involves shutting down the servers installing the new version binaries on each and restarting them.

You should read:

https://www.postgresql.org/support/versioning/

It would be a good idea to go through the Release Notes here:

https://www.postgresql.org/docs/15/release.html
To see what changed.

>
> Your guidance and recommendations on these questions will be greatly <= br> > appreciated.
>
> Thank you for your time and support!
>
> Best regards,
>
> Subhash
>

--
Adrian Klaver
adrian.klave= r@aklaver.com

--00000000000092b5bf0627ab377c--