From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
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 22:27:53 |
Message-ID: | 943.1558650473@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | buildfarm-members pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2019-05-23 14:05:19 -0400, Tom Lane wrote:
>> 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.
> Well, doing it for every single inline function is pretty annoying, just
> from a bulkiness perspective.
Oh, I certainly wasn't suggesting we do that.
> And figuring out exactly which inline
> function needs this isn't easy without something that actually shows the
> problem.
... which is why we need a buildfarm animal that shows the problem.
We had some, up until the C99 move.
If the only practical way to detect the issue were to run some ancient
platform or other, I'd tend to agree with you that it's not worth the
trouble. But if we can spot it just by using -fkeep-inline-functions
on an animal or two, I think it's a reasonable thing to keep supporting
the case for a few years more.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-06-04 12:02:08 | Please update buildfarm members to current script version (REL_10) |
Previous Message | Andres Freund | 2019-05-23 18:49:08 | Re: FullTransactionId changes are causing portability issues |
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2019-05-23 22:31:30 | Re: pg_dump throwing "column number -1 is out of range 0..36" on HEAD |
Previous Message | Tom Lane | 2019-05-23 22:23:45 | Re: ClosePipeStream failure ignored in pg_import_system_collations |