Feedback-ID: i76984098:Fastmail
Message-ID: <b465b0d4-5516-46e0-8a60-e24a05169566@aklaver.com>
Date: Fri, 24 Oct 2025 21:36:56 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Index corruption issue after migration from RHEL 7 to RHEL 9
 (PostgreSQL 11 streaming replication)
To: David Rowley <dgrowleyml@gmail.com>
Cc: Ron Johnson <ronljohnsonjr@gmail.com>,
 "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
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>
 <CANzqJaBq3hcAUXhSi5ar0=Gw0QxqfmD_E47dxHAex9_D3Yv-WA@mail.gmail.com>
 <2b09033b-d375-488d-9188-17a0f214e823@aklaver.com>
 <CAApHDvo5pLSwD4JVxW8t94Vc88djKrrSyrL-GbQJ=hb2NVT5zg@mail.gmail.com>
 <4babadbd-cc61-43e7-b7fb-3053dcdaadac@aklaver.com>
 <CAApHDvq5-7UO1PZBcizg13_ptE0mP=iKwFKUHqhKjwTmS6YR-A@mail.gmail.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <CAApHDvq5-7UO1PZBcizg13_ptE0mP=iKwFKUHqhKjwTmS6YR-A@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/b465b0d4-5516-46e0-8a60-e24a05169566%40aklaver.com>
Precedence: bulk

On 10/24/25 18:06, David Rowley wrote:
> On Sat, 25 Oct 2025 at 13:40, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
>>

>> 2) The attitude comes from lessons learned in the School of Hard Knocks.
>> Until someone or someones can guarantee a new GA release will not eat
>> your data or spring security leaks then the prudent thing to do is wait
>> to see what happens when it hits the world at large. I learned this
>> lesson, pitfalls of jumping into something new, across fields outside of
>> software as well. In other words 'new and improved' is not always the
>> case, see 737 MAX as case in point.
> 
> I don't see why this reason is applicable at all to my statement. I
> didn't state that everyone should go and run with .0. I said we
> shouldn't encourage people to test beta and RC versions, as if they
> don't do that then .0 won't be as stable as if they did test (and
> report issues). It seems like simple cause and effect to me.

I am not following, from your previous post:

"Beta versions are meant for test instances. It'd be
good if people encouraged their use more often rather than pushing
people to defer til GA"

That seems to be the opposite of what you say above.

> 
>> 3) Progress happens and you need to keep up. A little caution is good
>> thing though, especially if you are the one who is being held
>> responsible for any adverse outcomes.
> 
> We're talking test servers here. I assume they can be recreated
> without too much trouble.

Yes, but the OP was talking about upgrading a production database 
directly to 18. That was what my reply was referring to and what I was 
counseling against.

> 
> David


-- 
Adrian Klaver
adrian.klaver@aklaver.com