MIME-Version: 1.0
References: <CAJ4rSwspyYBppQS701C=BVFX2yrP1JErgDCZXbC15BQh2zAS1Q@mail.gmail.com>
 <CAKAnmmK47O_rYDB4iPe=K3QiqzJcCnnxCoYs_40Q1YWb=x0nDg@mail.gmail.com>
 <CAJ4rSwvsRJhwfuem0vsws1WwRZPN8Ju2Nw0e0Oc2j7n=MXUhMg@mail.gmail.com>
 <8d340169-b500-4048-a665-0700813313a3@aklaver.com> <CAKAnmmLDfgYRX8oC6S7jKZyovv6wy72Twq6-hx315GKTowMjew@mail.gmail.com>
 <c319a69b-a667-4536-9aba-d75a4235b786@aklaver.com>
In-Reply-To: <c319a69b-a667-4536-9aba-d75a4235b786@aklaver.com>
From: Ron Johnson <ronljohnsonjr@gmail.com>
Date: Fri, 24 Oct 2025 11:00:35 -0400
Message-ID: <CANzqJaBq3hcAUXhSi5ar0=Gw0QxqfmD_E47dxHAex9_D3Yv-WA@mail.gmail.com>
Subject: Re: Index corruption issue after migration from RHEL 7 to RHEL 9
 (PostgreSQL 11 streaming replication)
To: "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000009d0c100641e8d09d"
Archived-At: <https://www.postgresql.org/message-id/CANzqJaBq3hcAUXhSi5ar0%3DGw0QxqfmD_E47dxHAex9_D3Yv-WA%40mail.gmail.com>
Precedence: bulk

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

On Fri, Oct 24, 2025 at 10:54=E2=80=AFAM Adrian Klaver <adrian.klaver@aklav=
er.com>
wrote:

> On 10/24/25 05:53, Greg Sabino Mullane wrote:
> > On Thu, Oct 23, 2025 at 11:49=E2=80=AFAM Adrian Klaver
> > <adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>> wrote:
> >
> >     I am not sure version 18 would a good choice at this time, it has
> >     just been released and has no bug fix releases against it yet. Give=
n
> >     the
> >     other complications in your upgrade, OS upgrade and multi-version
> >     jump, I don't think you want to add a brand new version to the mix.
> >     Postgres
> >     17 on the other hand has been out a year and has had 6 bug/security
> >     fixes. It is probably a more stable target version.
> >
> >
> > I hear your concern, but I'm pretty confident in v18. Additionally, the=
y
>
> Which is pretty much the criteria for a GA release, confidence that it
> is ready to face the general public. That is not the same thing as it
> being guaranteed bug free. Only time facing the manipulations of said
> public proves how many bugs there are and how bad they are.
>

"Never trust a .0 release with important data" is just as true in 2025 as
it was in 1985.

That's a chicken and egg problem, though, isn't it?

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

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

<div dir=3D"ltr"><div dir=3D"ltr">On Fri, Oct 24, 2025 at 10:54=E2=80=AFAM =
Adrian Klaver &lt;<a href=3D"mailto:adrian.klaver@aklaver.com">adrian.klave=
r@aklaver.com</a>&gt; wrote:</div><div class=3D"gmail_quote gmail_quote_con=
tainer"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 10/24/25 05:53=
, Greg Sabino Mullane wrote:<br>
&gt; On Thu, Oct 23, 2025 at 11:49=E2=80=AFAM Adrian Klaver <br>
&gt; &lt;<a href=3D"mailto:adrian.klaver@aklaver.com" target=3D"_blank">adr=
ian.klaver@aklaver.com</a> &lt;mailto:<a href=3D"mailto:adrian.klaver@aklav=
er.com" target=3D"_blank">adrian.klaver@aklaver.com</a>&gt;&gt; wrote:<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0I am not sure version 18 would a good choice at thi=
s time, it has<br>
&gt;=C2=A0 =C2=A0 =C2=A0just been released and has no bug fix releases agai=
nst it yet. Given<br>
&gt;=C2=A0 =C2=A0 =C2=A0the<br>
&gt;=C2=A0 =C2=A0 =C2=A0other complications in your upgrade, OS upgrade and=
 multi-version<br>
&gt;=C2=A0 =C2=A0 =C2=A0jump, I don&#39;t think you want to add a brand new=
 version to the mix.<br>
&gt;=C2=A0 =C2=A0 =C2=A0Postgres<br>
&gt;=C2=A0 =C2=A0 =C2=A017 on the other hand has been out a year and has ha=
d 6 bug/security<br>
&gt;=C2=A0 =C2=A0 =C2=A0fixes. It is probably a more stable target version.=
<br>
&gt; <br>
&gt; <br>
&gt; I hear your concern, but I&#39;m pretty confident in v18. Additionally=
, they <br>
<br>
Which is pretty much the criteria for a GA release, confidence that it <br>
is ready to face the general public. That is not the same thing as it <br>
being guaranteed bug free. Only time facing the manipulations of said <br>
public proves how many bugs there are and how bad they are.<br></blockquote=
><div><br></div><div></div></div><div>&quot;Never trust a .0 release with i=
mportant data&quot; is just as true in 2025 as it was in 1985.</div><div><b=
r></div><div>That&#39;s a chicken and egg problem, though, isn&#39;t it?</d=
iv><div><br></div><span class=3D"gmail_signature_prefix">-- </span><br><div=
 dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr">Death to &lt;Redact=
ed&gt;, and butter sauce.<div>Don&#39;t boil me, I&#39;m still alive.<br><d=
iv><div>&lt;Redacted&gt; lobster!</div></div></div></div></div></div>

--0000000000009d0c100641e8d09d--