Re: narwhal and PGDLLIMPORT
Amit Kapila <amit.kapila16@gmail.com>
From: Amit Kapila <amit.kapila16@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2014-02-03T04:20:55Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
MinGW: Link with shell32.dll instead of shfolder.dll.
- 53566fc0940c 9.5.0 cited
-
Centralize getopt-related declarations in a new header file pg_getopt.h.
- 60ff2fdd9970 9.4.0 cited
-
Get rid of use of dlltool in Mingw builds.
- 846e91e0223c 9.4.0 cited
-
Export a few more symbols required for test_shm_mq module.
- 7d7eee8bb702 9.4.0 cited
-
Export set_latch_on_sigusr1 symbol for Windows.
- 708c529c7fde 9.4.0 cited
-
Use SHGetFolderPath instead of SHGetSpecialFolderPath to find the
- 889f03812916 8.1.0 cited
On Sun, Feb 2, 2014 at 6:33 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > I happened to notice today that the owner of buildfarm member narwhal > is trying to revive it after a long time offline, but it's failing in > the 9.3 branch (and not attempting to build HEAD, yet). The cause > appears to be that contrib/postgres_fdw is referencing the DateStyle > and IntervalStyle variables, which aren't marked PGDLLIMPORT. > Hm, well, that would be an easy change ... but that code was committed > last March. How is it that we didn't notice this long ago? > > What this seems to indicate is that narwhal is the only buildfarm > animal that has a need for PGDLLIMPORT marks on global variables that > are referenced by extensions. I have tried to debug the part of code where we are using DateStyle and IntervalStyle variables in postgres_fdw on my m/c (Win 7 - 64 bit, MSVC2010) and found that there value is junk, to me the problem looks exactly similar to what we have seen for test_shm_mq modules few days back. I am not sure why it is passing on other buildfarm m/c, but I think we need to put PGDLLIMPORT for global variables we want to use in extensions. Also as per below link, it seems that PGDLLIMPORT is required for exported global variables. http://msdn.microsoft.com/en-us/library/8fskxacy(v=vs.80).aspx With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com