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 1vCSKK-00EIwK-7l for pgsql-general@arkaria.postgresql.org; Sat, 25 Oct 2025 00:40:11 +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 1vCSKH-001dLt-LM for pgsql-general@arkaria.postgresql.org; Sat, 25 Oct 2025 00:40:08 +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 1vCSKG-001dLk-Mq for pgsql-general@lists.postgresql.org; Sat, 25 Oct 2025 00:40:08 +0000 Received: from fhigh-a4-smtp.messagingengine.com ([103.168.172.155]) by makus.postgresql.org with smtp (Exim 4.96) (envelope-from ) id 1vCSKD-003ckp-28 for pgsql-general@lists.postgresql.org; Sat, 25 Oct 2025 00:40:06 +0000 Received: from phl-compute-02.internal (phl-compute-02.internal [10.202.2.42]) by mailfhigh.phl.internal (Postfix) with ESMTP id B4F49140035A; Fri, 24 Oct 2025 20:40:04 -0400 (EDT) Received: from phl-mailfrontend-02 ([10.202.2.163]) by phl-compute-02.internal (MEProxy); Fri, 24 Oct 2025 20:40:04 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm1; t=1761352804; x=1761439204; bh=DYbluBoahQKfn9kQE/gs2FOBGkpmoHbDMxzkpWuE/Rw=; b= OAgEEqx9XAntDo8iLP8vB/Tur5GRWDWtVnUt9OTE0E38orkbWW5AjLPQcRjuawCs 4BPisv1FYv1qa3wouNHHE7oc5Lpomr1zHBvFaPNsT5iwcvkF/udnSww7RQhgJwEE 1kBMVt1wnQKhn7XGcw58R5jaU/bl50b1H7Qk3R/ogsu8aDx4OYsQzyF4w1F1SJrH Q3TRhMlTYI/qoU/ORWbVwg5vjQtv4JghChR2QczbEEMqR7TjOpu9yuIEDAgZrEGo Xu/dBTH4mxrEbvs0aXBHuW7qW0ttODg7Z7eEEIbjX8XHOG2SqKRP5HJsXYcn1bBD UKNjV90917/XhzXGQ/5BZA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1761352804; x= 1761439204; bh=DYbluBoahQKfn9kQE/gs2FOBGkpmoHbDMxzkpWuE/Rw=; b=T xpdWoYQhL3aToLUHiOmmEUdurNE1lREyjt50WIiliAORUYEv755VqQVAdEkT9hwN 3qE+yW0LVzrLIrMqGjztCwU1VYpNDYBQpSMxsNDNxAEndQkFIqR+ITRqNFbIAjAH w56L4XconuinliHiq/Qp4Wls7JcoQhurRp1fPTBD3pFzGqMHilZCF6w+Dkk9y+3A 5wxYl6MwHDzrSaxzl6wxK6voGA6wxZJ1wjWFB6fs+/6pL5gZGJRpSJ9dup8siPnI B5cQ8DLZ5YChc3N3iKc2cFHCMOJYCK0yRWNkB09W1zB/h0HBxdNotWP5Ej2Lb7vd 0+UKK6GZjY5+HmPsa+rmA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdeggdduhedtkedtucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujf gurhepkfffgggfuffvvehfhfgjtgfgsehtkeertddtvdejnecuhfhrohhmpeetughrihgr nhcumfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomh eqnecuggftrfgrthhtvghrnhepfeegfeeiuedtgffgteeggfehkeejheetieeliefgteei keejvdeiveeigfehvedtnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomheprggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomhdpnhgs pghrtghpthhtohepfedpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepughgrhhofi hlvgihmhhlsehgmhgrihhlrdgtohhmpdhrtghpthhtoheprhhonhhljhhohhhnshhonhhj rhesghhmrghilhdrtghomhdprhgtphhtthhopehpghhsqhhlqdhgvghnvghrrghlsehlih hsthhsrdhpohhsthhgrhgvshhqlhdrohhrgh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 24 Oct 2025 20:40:03 -0400 (EDT) Message-ID: <4babadbd-cc61-43e7-b7fb-3053dcdaadac@aklaver.com> Date: Fri, 24 Oct 2025 17:40:03 -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 Cc: Ron Johnson , "pgsql-generallists.postgresql.org" References: <8d340169-b500-4048-a665-0700813313a3@aklaver.com> <2b09033b-d375-488d-9188-17a0f214e823@aklaver.com> Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 10/24/25 15:37, 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 AM Adrian Klaver >>> > 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 > good if people encouraged their use more often rather than pushing > people to defer til GA. 1) From previous posts to this list folks have mentioned their organizations prohibit touching anything less then a GA or maybe a late RC. That comes from on high and I doubt the folks issuing the orders are on this list. 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. 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. > > David -- Adrian Klaver adrian.klaver@aklaver.com