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/

In response to

• Re: BUG #5394: invalid declspec for PG_MODULE_MAGIC at 2010-03-29 09:47:05 from Takahiro Itagaki

Responses

• Re: BUG #5394: invalid declspec for PG_MODULE_MAGIC at 2010-04-06 19:55:01 from Tom Lane

pgsql-hackers by date

Next:	From: Merlin Moncure	Date: 2010-04-06 17:47:56
	Subject: Re: SELECT constant; takes 15x longer on 9.0?
Previous:	From: Tom Lane	Date: 2010-04-06 17:31:49
	Subject: Re: Proposal: Add JSON support

pgsql-bugs by date

Next:	From: Josh Berkus	Date: 2010-04-06 19:42:12
	Subject: Re: Re: regexp_matches illegally restricts rows -- just a documentation issue?
Previous:	From: Robert Haas	Date: 2010-04-06 16:10:00
	Subject: Re: Re: regexp_matches illegally restricts rows -- just a documentation issue?