Re: narwhal and PGDLLIMPORT - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: narwhal and PGDLLIMPORT
Date
Msg-id 52FACF60.3070404@dunslane.net
Whole thread Raw
In response to Re: narwhal and PGDLLIMPORT  (Craig Ringer <craig@2ndquadrant.com>)
Responses Re: narwhal and PGDLLIMPORT  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 02/11/2014 08:04 PM, Craig Ringer wrote:
> 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.
>
>


It sure used to: 
<http://www.pgbuildfarm.org/cgi-bin/show_stage_log.pl?nm=currawong&dt=2014-02-03%2005%3A30%3A00&stg=make>

cheers

andrew




pgsql-hackers by date:

Previous
From: Mark Kirkwood
Date:
Subject: Per table autovacuum vacuum cost limit behaviour strange
Next
From: Tom Lane
Date:
Subject: Re: Unhappy with error handling in psql's handleCopyOut()