From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
Cc: | Vladimir Barzionov <snego(dot)barsik(at)gmail(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: BUG #5394: invalid declspec for PG_MODULE_MAGIC |
Date: | 2010-04-06 17:39:56 |
Message-ID: | r2n9837222c1004061039n139ea2ccg2df2b99e8a9781e4@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On Mon, Mar 29, 2010 at 11:47 AM, Takahiro Itagaki
<itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> wrote:
>
> "Vladimir Barzionov" <snego(dot)barsik(at)gmail(dot)com> wrote:
>
>> Same problem was already discussed for example here
>> http://dbaspot.com/forums/postgresql/393683-re-general-custom-c-function-palloc-broken.html
>>
>> Looks like the simplest way for correcting the issue is declaring additional
>> macro (something like PGMODULEEXPORT)
>
> Sure, I agree it is a longstanding bug in PostgreSQL. Developers who use
> MSVC (not mingw) always encounter the bug; machines in the buildfarm can
> build Windows binaries just because they have non-standard equipments.
>
> A patch attached. The name of "PGMODULEEXPORT" might be arguable.
I agree with this in principle, but won't this break every single
add-on module out there that supports Win32?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2010-04-06 19:42:12 | Re: Re: regexp_matches illegally restricts rows -- just a documentation issue? |
Previous Message | Robert Haas | 2010-04-06 16:10:00 | Re: Re: regexp_matches illegally restricts rows -- just a documentation issue? |
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2010-04-06 17:47:56 | Re: SELECT constant; takes 15x longer on 9.0? |
Previous Message | Tom Lane | 2010-04-06 17:31:49 | Re: Proposal: Add JSON support |