Re: Mark all GUC variable as PGDLLIMPORT

Поиск
Список
Период
Сортировка
От Chapman Flack
Тема Re: Mark all GUC variable as PGDLLIMPORT
Дата
Msg-id 62098CD4.1010103@anastigmatix.net
обсуждение исходный текст
Ответ на Re: Mark all GUC variable as PGDLLIMPORT  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On 02/13/22 15:48, Tom Lane wrote:
> much fix any worries there.  Or we could provide APIs that let an
> extension look up a "struct config_generic *" once and then fetch
> directly using that pointer.  (But I'd prefer not to, since it'd
> constrain the internals more than I think is wise.)

There is GetConfigOptionByNum already ... but I'm not sure there's
an easy way to ask "what's the num for option foo?".

GetNumConfigOptions exists, so there is a brute-force way.

Regards,
-Chap



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

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set
Следующее
От: Tomas Vondra
Дата:
Сообщение: Re: [PATCH] Avoid open and lock the table Extendend Statistics (src/backend/commands/statscmds.c)