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 1tFFnf-00C8gQ-He for pgsql-general@arkaria.postgresql.org; Sun, 24 Nov 2024 16:49:31 +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 1tFFne-008WiE-7C for pgsql-general@arkaria.postgresql.org; Sun, 24 Nov 2024 16:49:30 +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 1tFFnd-008Wem-SC for pgsql-general@lists.postgresql.org; Sun, 24 Nov 2024 16:49:29 +0000 Received: from mail-oo1-xc32.google.com ([2607:f8b0:4864:20::c32]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tFFnb-003YjR-8o for pgsql-general@postgresql.org; Sun, 24 Nov 2024 16:49:28 +0000 Received: by mail-oo1-xc32.google.com with SMTP id 006d021491bc7-5f1e364cc22so92008eaf.2 for ; Sun, 24 Nov 2024 08:49:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1732466966; x=1733071766; darn=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=Fqdw5Sgl6w+H/VCid2VMvlLZV1JeT+VGVKopC2y+Lt0=; b=HGg4khubsuXuMb1hTpdEMPRisaFTGKk2vCk1uy7jqXRwM66I1BUjhU3Jp4M3qXyk71 iyI0MUayHNItUTQFwdvL2Y6BlqIvBDfpaa2I7tPQMqXlrLkmh0/eS2qzqGo1xU3z/7Gd dwg+3CM1Npzi+JRdf62fNMdtnJ3gj8y9jviQaRbZTKMxyefxjNxxpWVaeoohuuFh4yD5 J5CKvpQcTDT8kyj9Rssz8S5U6AXI7az7Nc7Uk0S6v42LaCrxuU3k0OH2MRyTJPSrgpfm SCWtUGksmgDEITd+R23LFla+flC6WDFeNmTetk8B04ImaKMB9Hl3oncyo8Q9N/u6CtRu L4Og== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732466966; x=1733071766; 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=Fqdw5Sgl6w+H/VCid2VMvlLZV1JeT+VGVKopC2y+Lt0=; b=uPM330WLFLazC2WmLGUHenkorZj2vy1lsQ0AAfPwJqfI2eZZCSO5EetvPTrSzSrMCw 1gj6zSHDrjAG8c7dgcizN0O1AR2C8D6sTM+m3Jklvk077ALWPsFduyBUv0nrThy1GN/7 92AfiVJ6JMsYB0EWEZrqHSn3Wo6HDBVvq7m1rVFKfzFbJze+s52w949xe1/303brShQv hZVbvnHCrbQFs8tZzkIg2Kjb7xtvztQjXqe6S0ZPbfeMs63DACJH84/SqFl6Ct0w9O9h HiqY1fp60GmH4uQFvaW4H7RVX4dM8hqL4EVwWVP9ZHvxbIGyvn6fVN8WaUBrqPN/B9sR 8MIA== X-Gm-Message-State: AOJu0Ywi1rVRDfMvcsRxHyGoGB59laDedTfdJN3AKjYCaDlvW05dNVeo tzSu+Ffm1iu1QaUI2VyVgy0/8WBls6H2Juziw33QnEMrFVzqBO4mGyrnZ79MX24VY/MVYcfVsH2 0nh68IwmWJgP+F2JfWC1oPm17aDlM0A== X-Gm-Gg: ASbGncvDpMvRomC4WUODyvNjHXRWtRFLwzJ1HhCZhatFLDV7xfaZ3t4Nh6dy9Nafbq/ 9m0eApRBuOh+rFrQ9MQrRWE1zkiexCOKCRbPZhT0xnVskpFT4IeXiCYZcA55C9RVJ7w== X-Google-Smtp-Source: AGHT+IHXN0vBVx53kJCtT1Qk4SCUnrYWhzIKDdLFovZFqbD4LQD6I7XxvFWFbPtwmsO4vLFXvTt2XoiFonY6tZTP7Ek= X-Received: by 2002:a05:6830:b93:b0:718:1163:ef8f with SMTP id 46e09a7af769-71c04b6ab61mr9743173a34.2.1732466966039; Sun, 24 Nov 2024 08:49:26 -0800 (PST) MIME-Version: 1.0 References: <6c498f0e-64f9-449a-9b90-5cd72d00e2ef@aklaver.com> <2a7d96ac-83a7-4ddc-a3ce-9c637f2c1c76@aklaver.com> In-Reply-To: <2a7d96ac-83a7-4ddc-a3ce-9c637f2c1c76@aklaver.com> From: Ron Johnson Date: Sun, 24 Nov 2024 11:49:15 -0500 Message-ID: Subject: Re: Questions on Upgrading PostgreSQL from 15.0 to 15.9 and Setting Up Streaming Replication To: pgsql-general Content-Type: multipart/alternative; boundary="0000000000001890e30627ab66d6" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000001890e30627ab66d6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, Nov 24, 2024 at 11:41=E2=80=AFAM Adrian Klaver wrote: > On 11/24/24 08:36, Subhash Udata wrote: > > 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 > > Sorry, I was not clear enough. When I said 'Why?' it was not referring > to reason you wanted to upgrade, it was why go through the whole > pg_basebackup process. Read this link: OP might not be able to tolerate any downtime. --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --0000000000001890e30627ab66d6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sun, Nov 24, 2024 at 11:41=E2=80=AFAM = Adrian Klaver <adrian.klave= r@aklaver.com> wrote:
On 11/24/24 08:36, Subhash Udata wrote:=
> The reason to upgrade from 15.0 to 15.9 is this
> https://www.postgresql.org/support/s= ecurity/CVE-2024-10979/
> <https://www.postgresql.org/suppo= rt/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

Sorry, I was not clear enough. When I said 'Why?' it was not referr= ing
to reason you wanted to upgrade, it was why go through the whole
pg_basebackup process. Read this link:

OP m= ight not be able to tolerate any downtime.
=C2=A0=C2=A0
--
Death to <Redacted>, and butt= er sauce.
Don't boil me, I'm still alive.
<Reda= cted> lobster!
--0000000000001890e30627ab66d6--