| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: narwhal and PGDLLIMPORT |
| Date: | 2014-02-02 01:28:41 |
| Message-ID: | 25333.1391304521@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> On 2014-02-01 20:03:58 -0500, Tom Lane wrote:
>> I think we should give serious consideration to desupporting this
>> combination so that we can get rid of the plague of PGDLLIMPORT
>> marks. Obviously this would depend on confirming that there are
>> no more-interesting Windows build methods that require it --- but
>> if there are any, I'd sure demand that there be an active buildfarm
>> instance to keep us from breaking the case again in future.
> Weren't there more recent cases of needing to add PGDLLIMPORTs?
Yeah, which makes the plot even thicker. If references to those
variables failed, how did we not notice postgres_fdw's issue?
I don't claim to know exactly what's going on, but I think we need
to find out.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-02-02 02:04:44 | Re: narwhal and PGDLLIMPORT |
| Previous Message | Andres Freund | 2014-02-02 01:25:35 | Re: narwhal and PGDLLIMPORT |