| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: currawong is not a happy animal |
| Date: | 2014-01-17 17:55:05 |
| Message-ID: | CAApHDvq+cfCs31yfK1-khhO+OkG=psY_6YuC=gCEfvw0Gfd+uA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Jan 18, 2014 at 6:50 AM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
> On 01/17/2014 12:43 PM, Tom Lane wrote:
>
>> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>>
>>> It looks like what we need to fix the immediate problem is to mark
>>> set_latch_on_sigusr1 with PGDLLIMPORT. Is that the only one of these
>>> symbols we might need to make visible?
>>>
>> We've generally relied on the buildfarm to cue us to add PGDLLIMPORT.
>> Add that one and see what happens ...
>>
>>
>>
>
>
> OK, done.
>
>
Great, that fixes it on my end.
Thanks for fixing those.
Regards
David Rowley
> cheers
>
> andrew
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mel Gorman | 2014-01-17 18:34:25 | Re: [Lsf-pc] Re: Linux kernel impact on PostgreSQL performance (summary v2 2014-1-17) |
| Previous Message | Andrew Dunstan | 2014-01-17 17:50:10 | Re: currawong is not a happy animal |