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

From Julien Rouhaud
Subject Re: Mark all GUC variable as PGDLLIMPORT
Date
Msg-id CAOBaU_YkPBHQKB1E_OaAj1tLioP1m=b-tuqPyNeeqfS1J7KdRg@mail.gmail.com
Whole thread Raw
In response to Mark all GUC variable as PGDLLIMPORT  (Julien Rouhaud <rjuju123@gmail.com>)
Responses Re: Mark all GUC variable as PGDLLIMPORT  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List pgsql-hackers
On Mon, Aug 23, 2021 at 10:36 PM Bruce Momjian <bruce@momjian.us> wrote:
>
> So the problem is that extensions only _need_ to use that API on
> Windows, so many initially don't, or that the API is too limited?

The inconvenience with that API is that it's only returning c strings,
so you gave to convert it back to the original datatype.  That's
probably why most of the extensions simply read from the original
exposed variable rather than using the API, because they're usually
written on Linux or similar, not because they want to mess up the
stored value.



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Queries that should be canceled will get stuck on secure_write function
Next
From: Julien Rouhaud
Date:
Subject: Re: Mark all GUC variable as PGDLLIMPORT