Postgres Pro
Downloads
Home   >   mailing lists

Re: Mark all GUC variable as PGDLLIMPORT - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: Mark all GUC variable as PGDLLIMPORT
Date
Msg-id CAGRY4nw55K-pJPsDsGHiaRsaBLjmtvGF2rWQiPQmm0_7wavNNQ@mail.gmail.com
Whole thread Raw
In response to Re: Mark all GUC variable as PGDLLIMPORT  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
Tree view
On Thu, 26 Aug 2021 at 01:51, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
On 2021-Aug-25, Magnus Hagander wrote:

> The thing we need the PGDLLIMPORT definition for is to *import* them
> on the other end?

Oh ... so modules that are willing to cheat can include their own
declarations of the variables they need, and mark them __declspec
(dllimport)?


Damn. I was hoping nobody would notice that.

I do exactly that in some extensions to work around some of this mess, but it is quite awkward and has its limitations.

pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Mark all GUC variable as PGDLLIMPORT
Next
From: Craig Ringer
Date:
Subject: Re: Mark all GUC variable as PGDLLIMPORT