Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hTXbt-00040s-7U for pgsql-hackers@arkaria.postgresql.org; Wed, 22 May 2019 20:13:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hTXbr-0003Ds-SO for pgsql-hackers@arkaria.postgresql.org; Wed, 22 May 2019 20:13:11 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hTXbr-0003Dh-Jy; Wed, 22 May 2019 20:13:11 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hTXbp-0003zH-CV; Wed, 22 May 2019 20:13:11 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x4MKD28g012029; Wed, 22 May 2019 16:13:02 -0400 From: Tom Lane To: Andres Freund cc: buildfarm-members@lists.postgresql.org, pgsql-hackers@lists.postgresql.org Subject: Re: FullTransactionId changes are causing portability issues In-reply-to: <20190522200312.kmh6qv3jbms7dtpx@alap3.anarazel.de> References: <27054.1558533367@sss.pgh.pa.us> <6039.1558536488@sss.pgh.pa.us> <11261.1558554950@sss.pgh.pa.us> <20190522200312.kmh6qv3jbms7dtpx@alap3.anarazel.de> Comments: In-reply-to Andres Freund message dated "Wed, 22 May 2019 13:03:12 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <12027.1558555982.1@sss.pgh.pa.us> Date: Wed, 22 May 2019 16:13:02 -0400 Message-ID: <12028.1558555982@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Andres Freund writes: > On 2019-05-22 15:55:50 -0400, Tom Lane wrote: >>> So the disturbing thing here is that we no longer have any active >>> buildfarm members that can build HEAD but have the won't-elide- >>> unused-static-functions problem. Clearly we'd better close that >>> gap somehow ... anyone have an idea about how to test it better? > I'm somewhat inclined to just declare that people using such old > compilers ought to just use something newer. Having to work around > broken compilers that are so old that we don't even have a buildfarm > animal actually exposing that behaviour, seems like wasted effort. IMO > it'd make sense to just treat this as part of the requirements for a C99 > compiler. TBH, I too supposed the requirement for this had gone away with the C99 move. But according to the discussion today on -packagers, there are still supported variants of Solaris that have compilers that speak C99 but don't have this behavior. Per Bjorn's report: >> The compiler used in Sun Studio 12u1, very old and and I can try to >> upgrade and see if that helps. > I tried Sun Studio 12u2 and then a more drastic upgrade to Developer > Studio 12.5 but both had the same effect. It doesn't sound like "use a newer compiler" is going to be a helpful answer there. (It is annoying that nobody is running such a platform in the buildfarm, I agree. But I don't have the resources to spin up a real-Solaris buildfarm member.) regards, tom lane