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 1hTs5v-0004lS-EZ for pgsql-hackers@arkaria.postgresql.org; Thu, 23 May 2019 18:05:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hTs5t-0008RW-P2 for pgsql-hackers@arkaria.postgresql.org; Thu, 23 May 2019 18:05:33 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hTs5t-0008QO-C2; Thu, 23 May 2019 18:05:33 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hTs5m-0002HJ-HW; Thu, 23 May 2019 18:05:31 +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 x4NI5JiN018539; Thu, 23 May 2019 14:05:19 -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: <20190523175231.qg7iq7tiucp2zgc2@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> <12028.1558555982@sss.pgh.pa.us> <20190523171134.vwsjumopzjnrgagn@alap3.anarazel.de> <17017.1558633575@sss.pgh.pa.us> <20190523175231.qg7iq7tiucp2zgc2@alap3.anarazel.de> Comments: In-reply-to Andres Freund message dated "Thu, 23 May 2019 10:52:31 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <18537.1558634719.1@sss.pgh.pa.us> Date: Thu, 23 May 2019 14:05:19 -0400 Message-ID: <18538.1558634719@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Andres Freund writes: > On 2019-05-23 13:46:15 -0400, Tom Lane wrote: >> I'm not really excited about adopting a position that PG will only >> build on GCC and clones thereof. > That's not what I said though? Not supporting one compiler, on an OS > that's effectively not being developed anymore, with a pretty > indefensible behaviour, requiring not insignificant work by everyone, > isn't the same as standardizing on gcc. I mean, we obviously are going > to continue at the absolute very least gcc, llvm/clang and msvc. I think you're vastly overstating the case for refusing support for this. Adding "#ifndef FRONTEND" to relevant headers isn't a huge amount of work --- it's certainly far less of a problem than the Microsoft-droppings we've had to put in in so many places. The only real issue in my mind is the lack of buildfarm support for detecting that we need to do so. Also relevant here is that you have no evidence for the assumption that these old Solaris compilers are the only live platform with the problem. Yeah, we wish our buildfarm covered everything of interest, but it does not. Maybe, if we get to beta2 without any additional reports of build failures on beta1, that would be a bit of evidence that nobody else cares --- but we have no such evidence right now. We certainly can't assume that any pre-v12 release provides evidence of that, because up till I retired pademelon, it was forcing us to keep this case supported. regards, tom lane