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

From Alvaro Herrera
Subject Re: Mark all GUC variable as PGDLLIMPORT
Date
Msg-id 202108251751.q33amh5dtm2y@alvherre.pgsql
Whole thread Raw
In response to Re: Mark all GUC variable as PGDLLIMPORT  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Mark all GUC variable as PGDLLIMPORT  (Julien Rouhaud <rjuju123@gmail.com>)
Re: Mark all GUC variable as PGDLLIMPORT  (Craig Ringer <craig.ringer@enterprisedb.com>)
List pgsql-hackers
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)?

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"The Gord often wonders why people threaten never to come back after they've
been told never to return" (www.actsofgord.com)



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: log_autovacuum in Postgres 14 -- ordering issue
Next
From: Robert Haas
Date:
Subject: Re: The Free Space Map: Problems and Opportunities