On Mon, Mar 29, 2010 at 11:47 AM, Takahiro Itagaki <itagaki.takah...@oss.ntt.co.jp> wrote: > > "Vladimir Barzionov" <snego.bar...@gmail.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/ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers