Re: narwhal and PGDLLIMPORT - Mailing list pgsql-hackers

From Tom Lane
Subject Re: narwhal and PGDLLIMPORT
Date
Msg-id 26804.1392223183@sss.pgh.pa.us
Whole thread Raw
In response to Re: narwhal and PGDLLIMPORT  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: narwhal and PGDLLIMPORT  (Andres Freund <andres@2ndquadrant.com>)
Re: narwhal and PGDLLIMPORT  (Bruce Momjian <bruce@momjian.us>)
Re: narwhal and PGDLLIMPORT  (Craig Ringer <craig@2ndquadrant.com>)
Re: narwhal and PGDLLIMPORT  (Marco Atzeri <marco.atzeri@gmail.com>)
List pgsql-hackers
Andres Freund <andres@2ndquadrant.com> writes:
> On 2014-02-12 11:26:56 -0500, Tom Lane wrote:
>> Hm.  So if we're giving up on the idea of ever getting rid of PGDLLIMPORT,
>> we ought to actually remove that, so that the Cygwin build works more like
>> the other Windows builds?

> Hm, I don't see a big advantage in detecting the errors as It won't
> hugely increase the buildfarm coverage. But --auto-import seems to
> require marking the .text sections as writable, avoiding that seems to
> be a good idea if we don't need it anymore.

Given the rather small number of Windows machines in the buildfarm,
I'd really like them all to be on the same page about what's valid
and what isn't.  Having to wait ~24 hours to find out if they're
all happy with something isn't my idea of a good time.  In any case,
as long as we have discrepancies between them, I'm not going to be
entirely convinced that any of them are telling the full truth.

I'm going to go remove that switch and see if brolga starts failing.
If it does, I'll be satisfied that we understand the issues here.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: narwhal and PGDLLIMPORT
Next
From: Andres Freund
Date:
Subject: Re: narwhal and PGDLLIMPORT