Date: Thu, 23 May 2019 10:52:31 -0700
From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: buildfarm-members@lists.postgresql.org,
	pgsql-hackers@lists.postgresql.org
Subject: Re: FullTransactionId changes are causing portability issues
Message-ID: <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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <17017.1558633575@sss.pgh.pa.us>
Precedence: bulk

Hi,

On 2019-05-23 13:46:15 -0400, Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
> > On 2019-05-22 16:13:02 -0400, Tom Lane wrote:
> >> It doesn't sound like "use a newer compiler" is going to be a helpful
> >> answer there.
> 
> > Well, GCC is available on solaris, and IIRC not that hard to install
> > (isn't it just a 'pkg install gcc' or such?). Don't think we need to
> > invest a lot of energy fixing a compiler / OS combo that effectively
> > isn't developed further.
> 
> 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.

Greetings,

Andres Freund