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 1tqahC-007Oeg-1C for buildfarm-members@arkaria.postgresql.org; Fri, 07 Mar 2025 16:37:10 +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 1tqahA-00BG6H-Pp for buildfarm-members@arkaria.postgresql.org; Fri, 07 Mar 2025 16:37:08 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tqahA-00BG5k-Jl for buildfarm-members@lists.postgresql.org; Fri, 07 Mar 2025 16:37:08 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tqah7-001Wzc-0X for buildfarm-members@lists.postgresql.org; Fri, 07 Mar 2025 16:37:08 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 527GavEx1023616; Fri, 7 Mar 2025 11:36:58 -0500 From: Tom Lane To: Stefan Kaltenbrunner cc: =?UTF-8?Q?=C3=81lvaro_Herrera?= , =?UTF-8?Q?Mikael_Kjellstr=C3=B6m?= , Peter Eisentraut , mikael.kjellstrom@gmail.com, buildfarm-members@lists.postgresql.org Subject: Re: please update description of grison In-reply-to: References: <202503070902.3f3djxxbiece@alvherre.pgsql> Comments: In-reply-to Stefan Kaltenbrunner message dated "Fri, 07 Mar 2025 10:18:27 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <1023614.1741365417.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Fri, 07 Mar 2025 11:36:57 -0500 Message-ID: <1023615.1741365417@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Stefan Kaltenbrunner writes: > On 07.03.25 10:02, Álvaro Herrera wrote: >> The fact that the compiler itself cannot be changed (say from gcc to >> clang, which you appear to be trying to do for sidewinder) appears to be >> on purpose. I suppose you should submit a new request and abandon the >> old animal name, if you wanted to make such a conversion. (I don't >> necessarily agree with this view of things, but it's how it is at >> present.) > yeah, I think this whole area could do with some rethinking - it is > _very_ common for people upgrading operating systems or even running > operating systems that are doing a continous upgrade thing. The idea is that switching to a whole new OS or compiler really does result in a different animal, which should have a different name to reduce confusion. (I didn't make this decision, but it seems reasonable to me.) Upgrades are fine, but those should only be moving the version numbers. > ... ideally I would expect the buildfarm itself to update the OS and > compiler version - what we have now is basically always outdated and wrong. Yeah, ideally we would not bother with the manual labeling of versions. I know how to scrape compiler versions out of the build logs, and I always do that when I am interested in compiler versions, rather than trusting the labels. But it's much harder to identify OS version from the build logs ... regards, tom lane