Re: FullTransactionId changes are causing portability issues

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: buildfarm-members(at)lists(dot)postgresql(dot)org, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: FullTransactionId changes are causing portability issues
Date: 2019-05-23 17:52:31
Message-ID: 20190523175231.qg7iq7tiucp2zgc2@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: buildfarm-members pgsql-hackers

Hi,

On 2019-05-23 13:46:15 -0400, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)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

In response to

Responses

Browse buildfarm-members by date

  From Date Subject
Next Message Tom Lane 2019-05-23 18:05:19 Re: FullTransactionId changes are causing portability issues
Previous Message Tom Lane 2019-05-23 17:46:15 Re: FullTransactionId changes are causing portability issues

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2019-05-23 17:55:19 Re: fsync failure in durable_unlink ignored in xlog.c?
Previous Message Andres Freund 2019-05-23 17:48:21 Re: Minimal logical decoding on standbys