Re: narwhal and PGDLLIMPORT - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: narwhal and PGDLLIMPORT
Date
Msg-id 52FAC892.8080906@2ndquadrant.com
Whole thread Raw
In response to Re: narwhal and PGDLLIMPORT  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: narwhal and PGDLLIMPORT  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On 02/12/2014 08:30 AM, Tom Lane wrote:
> Craig Ringer <craig@2ndquadrant.com> writes:
>> On 02/12/2014 07:22 AM, Tom Lane wrote:
>>> So the early returns from currawong are interesting:
> 
>> Great, that's what I was hoping to see - proper errors where we've
>> omitted things, not silent miscompilation.
> 
> Well, before you get too optimistic about that benighted platform ...
> mastodon just reported in on this patch, and it's showing a *different*
> set of unresolved symbols than currawong is.  None of them are a
> surprise exactly, but nonetheless, why didn't currawong find the
> postgres_fdw issues?
> 
> It still seems there's something unexplained here.

Looks like currawong doesn't build postgres_fdw.


-- Craig Ringer                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: narwhal and PGDLLIMPORT
Next
From: Mark Kirkwood
Date:
Subject: Per table autovacuum vacuum cost limit behaviour strange