Re: BUG #3983: pgxs files still missing in win32 install (8.3.1) - Mailing list pgsql-bugs

From Magnus Hagander
Subject Re: BUG #3983: pgxs files still missing in win32 install (8.3.1)
Date
Msg-id 48034763.5020004@hagander.net
Whole thread Raw
In response to Re: BUG #3983: pgxs files still missing in win32 install (8.3.1)  (Joe Conway <mail@joeconway.com>)
Responses Re: BUG #3983: pgxs files still missing in win32 install (8.3.1)  (Joe Conway <mail@joeconway.com>)
List pgsql-bugs
Joe Conway wrote:
> Magnus Hagander wrote:
>> In general, mingw built modules should load just fine in msvc built
>> postgres. AFAIK, that's how PostGIS does it for 8.3 (though I know Mark
>> is working on getting MSVC build support for them). Debugging may be a
>> bit harder (since they use different kinds of debug symbols - postgres
>> uses Windows style and mingw uses mingw style), but it should certainly
>> load.
>>
>> What trouble exactly are you seeing?
>
> Basically, "Procedure not found", even though it is there. Also note
> that the same R.dll is being used from the MinGW Postgres installation
> (where plr loads successfully) and the MSVC Postgres.

Could this be somethingl ike missing PGDLLIMPORT specifications in your
addon module or something like that? Try checking the names of the
functions that are actually exported using "depends" or a similar tool.


> postgres=# load '$libdir/dblink';
> LOAD
> postgres=# load '$libdir/plr';
> ERROR:  could not load library "C:/Program
> Files/PostgreSQL/8.3/lib/plr.dll": The specified procedure could not be
> found.

Actually, this looks like perhaps the backend is unable to load a DLL
that plr.dll depends on. Again, the "depends" tool can hopefully show
you what's missing there.

//Magnus

pgsql-bugs by date:

Previous
From: Euler Taveira de Oliveira
Date:
Subject: Re: BUG #4101: Fails to start when transaction log on another drive
Next
From: Joe Conway
Date:
Subject: Re: BUG #3983: pgxs files still missing in win32 install (8.3.1)