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 1vCQld-00Dz7e-8X for pgsql-general@arkaria.postgresql.org; Fri, 24 Oct 2025 23:00:16 +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 1vCQla-001NO4-TJ for pgsql-general@arkaria.postgresql.org; Fri, 24 Oct 2025 23:00:13 +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 1vCQla-001NNv-EE for pgsql-general@lists.postgresql.org; Fri, 24 Oct 2025 23:00:13 +0000 Received: from mail-oi1-x236.google.com ([2607:f8b0:4864:20::236]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vCQlT-003c0P-2z for pgsql-general@lists.postgresql.org; Fri, 24 Oct 2025 23:00:12 +0000 Received: by mail-oi1-x236.google.com with SMTP id 5614622812f47-445c6e9e0aaso1433960b6e.2 for ; Fri, 24 Oct 2025 16:00:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1761346807; x=1761951607; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=BAbHUVU/nK4gm4zYGr553Y5gWLHn7DuqIcep/RzjQ98=; b=a3bJs6/u9qiuffYOPqY3h9aMQQemG+rl5ZMYqv0Tr+WaZuSkCXtFFrmJaKEhqwaMM4 5m5bsSUuhAgLGQkO4zR2FR5rfmYGJMeiALS/7jlWWsjcvQ9E4ATfXoYEY5xDRmRQl85R Zy0KHx57HwLnzPu8F0+Aq7uZZfVP2YckM0Xn6NlC12rMMpfuu7v+kF4szSQYNCiFT/Gh 89ZT6dhMsXY4CjEVY4eT156Dxn1kG7T8M/6dgB4F59aW/nO2n0Xq8IQAxEOigcuLM54a gpLrrIeFYJoFoVz6c4AVZUojO3Bs+QSAVvyR2iPrGcLLcDj63NqCz7ucUwfzbCWnb/KX C6kg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1761346807; x=1761951607; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=BAbHUVU/nK4gm4zYGr553Y5gWLHn7DuqIcep/RzjQ98=; b=GgeQhe4j/RJbiA3rfmViDQCdFITZ1LA+nZuDBMfuf2vE/8DY1R4dwSF1Y2Fchub7vW mnj889q9/Mr9UzxnKKAsIdriWK4Q9C+4hXNy70GBith52lVY09dk4od6AKheuC3ezo2V qqvlMDs0tJlGlDFZtEDWX0x24DPjUl2tYeZ3vT45JrEjUvPaPmxjCBPsOW7+3cnqOLgG O5FE9xyNnmiVR8Ayv84h2wR+uEORJFbpMGT9IvAt3G06fNTKvHo5p0M9hH1QyMJxGGr3 XUnJEENWRxTGJFEFQaMiaJpZc3cWABZ8MJkH7/LMLHgF50HGI7BAEdgCMe4MnXOYSDom 5HjQ== X-Forwarded-Encrypted: i=1; AJvYcCVSi7PdDz+pZjoscOpxcEtA5Mjn+OI8T/YdqeVXiqhWDsCKcOiCsOCLMGDlnYGfED0lUBq/h6kOTLhycJnS@lists.postgresql.org X-Gm-Message-State: AOJu0YxI7k98mNGG/SHmGWOT2CAEkkTVysBrnQk/YjELJDyi2y7LpFje l5edFUqCdgTP+59F8OdQsEg1slRQJLU34e+dvlMPRACeYvRT+9aPGsqtb+LFpmPx4sHbaFMXDUv L8tMFjY2NL0lKPrhu6x+jjaH45B816GE= X-Gm-Gg: ASbGnct0w+cK2SEpHKRgE7GzFofutnKTBRYdQ98d89nX9N1ZVURdp/HJnpY4hA3sPGy x/3Mw2RCPaMfrJvMOVQGDIrjUAfqO/n7g4FClpLLYcxJZ+Qeeupx9oO5VbjVhsDucolYxvyHwEf tPTFFmZ95+pLVsl9Fz8Fyxe1BMVpTI7hwkYrNw67r+9AbRnMl5jrFvukiq7KkvE9Jp0/ZKMwPno EvwPwWUKWlc8MwxI8zvh059/9BaR1iDGWzPt4lCnpNNhFC0COuDPCfmotW/j/F5yj464tE= X-Google-Smtp-Source: AGHT+IEvM1QAEagDXWJXGiKKkdzWPOS7ibKk6u9nIfJqWH44CJyhg0gOYAmrCRiJNpseBoWGk9qjfBdnfh5R5b0zku0= X-Received: by 2002:a05:6808:2205:b0:438:3620:2ada with SMTP id 5614622812f47-443a2ea096emr11869126b6e.6.1761346806746; Fri, 24 Oct 2025 16:00:06 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a05:6802:1c0b:b0:603:160:c86c with HTTP; Fri, 24 Oct 2025 16:00:05 -0700 (PDT) In-Reply-To: References: <8d340169-b500-4048-a665-0700813313a3@aklaver.com> <2b09033b-d375-488d-9188-17a0f214e823@aklaver.com> From: "David G. Johnston" Date: Fri, 24 Oct 2025 19:00:05 -0400 X-Gm-Features: AS18NWBgtq-uclruN_UxNXrTjYgXxNcZdOFfO5JDHicHWscmxUYIzAeh7MRhxbo Message-ID: Subject: Re: Index corruption issue after migration from RHEL 7 to RHEL 9 (PostgreSQL 11 streaming replication) To: David Rowley Cc: Adrian Klaver , Ron Johnson , "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000be13650641ef820e" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000be13650641ef820e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Friday, October 24, 2025, David Rowley wrote: > On Sat, 25 Oct 2025 at 04:51, Adrian Klaver > wrote: > > > > On 10/24/25 08:00, Ron Johnson wrote: > > > On Fri, Oct 24, 2025 at 10:54=E2=80=AFAM Adrian Klaver > > > > wrote: > > > > > "Never trust a .0 release with important data" is just as true in 202= 5 > > > as it was in 1985. > > > > > > That's a chicken and egg problem, though, isn't it? > > > > There is nothing stopping you from setting up a test instance and > > kicking the tires on a new release to see if your setup will work > > correctly. > > I'd say it's exactly that attitude that causes people to think .0 > should be avoided. 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. > I=E2=80=99d say it=E2=80=99s negativity bias that causes this. Remembering= the times serious bugs were discovered in .0-.2 releases strongly leans one to avoid .0-.2 releases. Counteracting that bias with data seems needed. Yes, it would be great if more people tested betas; but there is no way for users to have any idea of how much or how effective such efforts have been for a given release. If someone comes here asking for advice I=E2=80=99m going to be conservativ= e. The ones who are going to be pushing the envelope or doing beta testing are not asking for this kind of advice. They do it likely to benefit from new features and some subset does it to be the canary for the community because they can handle the rare negative outcome. David J. --000000000000be13650641ef820e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Friday, October 24, 2025, David Rowley <dgrowleyml@gmail.com> wrote:
On Sat, 25 Oct 2025 at 04:51, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
>
> On 10/24/25 08:00, Ron Johnson wrote:
> > On Fri, Oct 24, 2025 at 10:54=E2=80=AFAM Adrian Klaver
> > <adrian.klaver@ak= laver.com <mailto:adria= n.klaver@aklaver.com>> wrote:
>
> > "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?
>
> There is nothing stopping you from setting up a test instance and
> kicking the tires on a new release to see if your setup will work
> correctly.

I'd say it's exactly that attitude that causes people to think .0 should be avoided. Beta versions are meant for test instances. It'd be<= br> good if people encouraged their use more often rather than pushing
people to defer til GA.

I=E2=80=99d say it=E2=80=99s negativity bi= as that causes this.=C2=A0 Remembering the times serious bugs were discover= ed in .0-.2 releases strongly leans one to avoid .0-.2 releases.=C2=A0 Coun= teracting that bias with data seems needed.=C2=A0 Yes, it would be great if= more people tested betas; but there is no way for users to have any idea o= f how much or how effective such efforts have been for a given release.

If someone comes here asking for advice I=E2=80=99m g= oing to be conservative.=C2=A0 The ones who are going to be pushing the env= elope or doing beta testing are not asking for this kind of advice.=C2=A0 T= hey do it likely to benefit from new features and some subset does it to be= the canary for the community because they can handle the rare negative out= come.

David J.

--000000000000be13650641ef820e--