MIME-Version: 1.0
References: <CAONZJQkaLtHeNz3P5wO8-EWPjOJ1M5fgyp8x4Mc4bb_U9n9_6g@mail.gmail.com>
 <7b5846ac-c16e-48d3-b548-99a772a528c5@aklaver.com> <CAD=40Z3G8z6d1BMDmQVAAPWzCzK5kbU9wWTCZA58qmq8-L=eoA@mail.gmail.com>
 <CAKFQuwbW-5yyVPCjyTJ0uwZZvn9J94s1XzuFnoBbMXp3BC3XyQ@mail.gmail.com>
 <CAD=40Z2+84YNSM7oMb4QBpuAaadk=9XRw3PGEu5Ui_YsWpmtFA@mail.gmail.com>
 <6c898e6499036ce70ac113b52df5c3ff06286a6a.camel@cybertec.at>
 <Z0A6Eg2FH2Nb5sWO@pureos> <Z0IafWDrFln-n0P5@momjian.us>
In-Reply-To: <Z0IafWDrFln-n0P5@momjian.us>
From: Greg Sabino Mullane <htamfids@gmail.com>
Date: Sat, 23 Nov 2024 13:30:13 -0500
Message-ID: <CAKAnmmLHR_WfR0yZhU9c_vT-hTU-T+N84mEvL6tTELoMLvySfw@mail.gmail.com>
Subject: Re: CVE-2024-10979 Vulnerability Impact on PostgreSQL 11.10
To: Bruce Momjian <bruce@momjian.us>
Cc: Matthias Apitz <guru@unixarea.de>, Laurenz Albe <laurenz.albe@cybertec.at>, 
	Subhash Udata <subhashudata@gmail.com>, "David G. Johnston" <david.g.johnston@gmail.com>, 
	Adrian Klaver <adrian.klaver@aklaver.com>, =?UTF-8?B?6rmA7KO87Jew?= <mysylph@gmail.com>, 
	"pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000e3e85b062798b2ea"
Archived-At: <https://www.postgresql.org/message-id/CAKAnmmLHR_WfR0yZhU9c_vT-hTU-T%2BN84mEvL6tTELoMLvySfw%40mail.gmail.com>
Precedence: bulk

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

On Sat, Nov 23, 2024 at 1:10=E2=80=AFPM Bruce Momjian <bruce@momjian.us> wr=
ote:

> and say bounce the database server and install the binaries.  What I
> have never considered before, and I should have, is the complexity of
> doing this for many remote servers.  Can we improve our guidance for
> these cases?
>

Hmm I'm not sure what else we can say. Our upgrade process is already
drop-dead-simple, especially compared to many (most?) other products out
there. People painting themselves into corners is not something we can
really help with.

Cheers,
Greg

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

<div dir=3D"ltr"><div dir=3D"ltr">On Sat, Nov 23, 2024 at 1:10=E2=80=AFPM B=
ruce Momjian &lt;<a href=3D"mailto:bruce@momjian.us">bruce@momjian.us</a>&g=
t; wrote:</div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);p=
adding-left:1ex">and say bounce the database server and install the binarie=
s.=C2=A0 What I<br>
have never considered before, and I should have, is the complexity of<br>
doing this for many remote servers.=C2=A0 Can we improve our guidance for<b=
r>
these cases?<br></blockquote><div><br></div><div>Hmm I&#39;m not sure what =
else we can say. Our upgrade process is already drop-dead-simple, especiall=
y compared to many (most?) other products out there. People painting themse=
lves into corners is not something we can really help with.</div><div><br><=
/div><div>Cheers,</div><div>Greg</div><div><br></div></div></div>

--000000000000e3e85b062798b2ea--