aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/jsonfuncs.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2016-10-12 18:01:43 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2016-10-12 18:01:43 -0400
commit4f52fd3c6d28a4380a5afc51ae6f774c91837a38 (patch)
treea407f25fb3bfd24ce1ba2af8485c1f3f8a2a74ce /src/backend/utils/adt/jsonfuncs.c
parentc0a3b211bcb790a8d76022cb2b3ffe9795aaf5e9 (diff)
downloadpostgresql-4f52fd3c6d28a4380a5afc51ae6f774c91837a38.tar.gz
postgresql-4f52fd3c6d28a4380a5afc51ae6f774c91837a38.zip
Revert addition of PGDLLEXPORT in PG_FUNCTION_INFO_V1 macro.
This turns out not to be as harmless as I thought: MSVC will complain if it sees an "extern" declaration without PGDLLEXPORT and then one with. (Seems fairly silly, given that this can be changed after the fact by the linker, but there you have it.) Therefore, contrib modules that have extern's for V1 functions in header files are falling over in the buildfarm, since none of those externs are marked PGDLLEXPORT. We might or might not conclude that we're willing to plaster those declarations with PGDLLEXPORT in HEAD, but in any case there's no way we're going to ship this change in the back branches. Third-party authors would not thank us for breaking their code in a minor release. Hence, revert the addition of PGDLLEXPORT (but let's keep the extra info in the comment). If we do the other changes we can revert this commit in HEAD. Per buildfarm.
Diffstat (limited to 'src/backend/utils/adt/jsonfuncs.c')
0 files changed, 0 insertions, 0 deletions