MIME-Version: 1.0
References: <SA1PR02MB969837F0BEDE8CD64AE703958ECA2@SA1PR02MB9698.namprd02.prod.outlook.com>
 <b76f0f54cbf8bd4ebe84eecea44168f23fcc2074.camel@cybertec.at>
In-Reply-To: <b76f0f54cbf8bd4ebe84eecea44168f23fcc2074.camel@cybertec.at>
From: Ron Johnson <ronljohnsonjr@gmail.com>
Date: Thu, 6 Mar 2025 03:27:09 -0500
Message-ID: <CANzqJaBnOKu5BO_Bwe934ZbBr0m54RmWujEQQnS58qy2nLvHdw@mail.gmail.com>
Subject: Re: Asking for OK for a nasty trick to resolve PG CVE-2025-1094 i
To: pgsql-general <pgsql-general@postgresql.org>, "Abraham, Danny" <danny_abraham@bmc.com>
Content-Type: multipart/alternative; boundary="0000000000004c16b4062fa846cd"
Archived-At: <https://www.postgresql.org/message-id/CANzqJaBnOKu5BO_Bwe934ZbBr0m54RmWujEQQnS58qy2nLvHdw%40mail.gmail.com>
Precedence: bulk

--0000000000004c16b4062fa846cd
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Mar 6, 2025 at 3:12=E2=80=AFAM Laurenz Albe <laurenz.albe@cybertec.=
at>
wrote:

> [redirecting to pgsql-general]
>
> On Thu, 2025-03-06 at 07:39 +0000, Abraham, Danny wrote:
> > I have many customers using PG 15.3 happily, and I cannot just snap
> upgrade them all to 15.12.
>
> Why do you think you cannot do that?
> In the long run, you'll be sorry if you don't.
> It is just a matter of replacing the software and restarting the database
> server.
>

It really is that simple.  On Linux, at least, it takes me less than two
minutes to:
1. Pause streaming replication between 2 nodes.
2. Stop PG on both nodes.
3. Install the new software.
4. Start PG on both nodes.
5. Resume streaming replication.

That's using PowerShell to do everything; a noticeable part of that 110
seconds is the ssh overhead of logging in and out of servers over our
network, and even more is taken up by me scanning for errors between each
step, and then pasting the next set of commands.

If all your database servers are Windows, then the PS to stop, install and
start on a remote node *should* be even faster (especially if you don't
have replication).

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

--0000000000004c16b4062fa846cd
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Thu, Mar 6, 2025 at 3:12=E2=80=AFAM La=
urenz Albe &lt;<a href=3D"mailto:laurenz.albe@cybertec.at">laurenz.albe@cyb=
ertec.at</a>&gt; wrote:</div><div class=3D"gmail_quote gmail_quote_containe=
r"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left:1px solid rgb(204,204,204);padding-left:1ex">[redirecting to pgsql-=
general]<br>
<br>
On Thu, 2025-03-06 at 07:39 +0000, Abraham, Danny wrote:<br>
&gt; I have many customers using PG 15.3 happily, and I cannot just snap up=
grade them all to 15.12.<br>
<br>
Why do you think you cannot do that?<br>
In the long run, you&#39;ll be sorry if you don&#39;t.<br>
It is just a matter of replacing the software and restarting the database s=
erver.<br></blockquote><div><br></div><div>It really is that simple.=C2=A0 =
On Linux, at least, it takes me less than two minutes to:</div><div>1. Paus=
e streaming replication between 2 nodes.</div><div>2. Stop PG on both nodes=
.</div><div>3. Install the new software.</div><div>4. Start PG on both node=
s.</div><div>5. Resume streaming replication.</div><div><br></div><div>That=
&#39;s using PowerShell to do everything; a noticeable part of that 110 sec=
onds is the ssh overhead of logging in and out of servers over our network,=
 and even more is taken up by me scanning for errors between each step, and=
 then pasting the next set of commands.</div><div><br></div><div>If all you=
r database servers are Windows, then the PS to stop, install and start on a=
 remote node <i>should</i>=C2=A0be even faster (especially if you don&#39;t=
 have=C2=A0replication).</div><div><br></div></div><span class=3D"gmail_sig=
nature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature"><di=
v dir=3D"ltr">Death to &lt;Redacted&gt;, and butter sauce.<div>Don&#39;t bo=
il me, I&#39;m still alive.<br><div><div>&lt;Redacted&gt; lobster!</div></d=
iv></div></div></div></div>

--0000000000004c16b4062fa846cd--