Re: Mark all GUC variable as PGDLLIMPORT

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Mark all GUC variable as PGDLLIMPORT
Дата
Msg-id 107887.1629728571@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Mark all GUC variable as PGDLLIMPORT  (Julien Rouhaud <rjuju123@gmail.com>)
Ответы Re: Mark all GUC variable as PGDLLIMPORT
Список pgsql-hackers
Bruce Momjian <bruce@momjian.us> writes:
> On Mon, Aug 23, 2021 at 10:15:04AM -0400, Tom Lane wrote:
>> By that argument, *every* globally-visible variable should be marked
>> PGDLLIMPORT.  But the mere fact that two backend .c files need to access

> No, Julien says 99% need only the GUCs, so that is not the argument I am
> making.

That's a claim unbacked by any evidence that I've seen.  More to
the point, we already have a mechanism that extensions can/should
use to read and write GUC settings, and it's not direct access.

            regards, tom lane



В списке pgsql-hackers по дате отправления:

Предыдущее
От: vignesh C
Дата:
Сообщение: Re: Added schema level support for publication.
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: Queries that should be canceled will get stuck on secure_write function