Re: FullTransactionId changes are causing portability issues - Mailing list buildfarm-members

From Andres Freund
Subject Re: FullTransactionId changes are causing portability issues
Date
Msg-id 20190523175231.qg7iq7tiucp2zgc2@alap3.anarazel.de
Whole thread Raw
In response to Re: FullTransactionId changes are causing portability issues  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: FullTransactionId changes are causing portability issues  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: FullTransactionId changes are causing portability issues  (Tom Lane <tgl@sss.pgh.pa.us>)
List buildfarm-members
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



buildfarm-members by date:

Previous
From: Tom Lane
Date:
Subject: Re: FullTransactionId changes are causing portability issues
Next
From: Tom Lane
Date:
Subject: Re: FullTransactionId changes are causing portability issues