Re: narwhal and PGDLLIMPORT
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Craig Ringer <craig@2ndquadrant.com>
Cc: "Inoue, Hiroshi" <inoue@tpf.co.jp>, Andrew Dunstan <andrew@dunslane.net>,
Robert Haas <robertmhaas@gmail.com>,
Andres Freund <andres@2ndquadrant.com>,
Amit Kapila <amit.kapila16@gmail.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2014-02-12T00:30:48Z
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
Craig Ringer <craig@2ndquadrant.com> writes: > On 02/12/2014 07:22 AM, Tom Lane wrote: >> So the early returns from currawong are interesting: > Great, that's what I was hoping to see - proper errors where we've > omitted things, not silent miscompilation. Well, before you get too optimistic about that benighted platform ... mastodon just reported in on this patch, and it's showing a *different* set of unresolved symbols than currawong is. None of them are a surprise exactly, but nonetheless, why didn't currawong find the postgres_fdw issues? It still seems there's something unexplained here. regards, tom lane