Re: 003_check_guc.pl crashes if some extensions were loaded.
| От | Tom Lane |
|---|---|
| Тема | Re: 003_check_guc.pl crashes if some extensions were loaded. |
| Дата | |
| Msg-id | 2885775.1698881391@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: 003_check_guc.pl crashes if some extensions were loaded. (Michael Paquier <michael@paquier.xyz>) |
| Ответы |
Re: 003_check_guc.pl crashes if some extensions were loaded.
Re: 003_check_guc.pl crashes if some extensions were loaded. |
| Список | pgsql-hackers |
Michael Paquier <michael@paquier.xyz> writes:
> On Thu, Nov 02, 2023 at 12:28:05AM +0300, Anton A. Melnikov wrote:
>> "SELECT name
>> FROM pg_settings
>> WHERE NOT 'NOT_IN_SAMPLE' = ANY (pg_settings_get_flags(name)) AND
>> - name <> 'config_file'
>> + name <> 'config_file' AND name NOT LIKE '%.%'
>> ORDER BY 1");
> Wouldn't it be better to add a qual as of "category <> 'Customized
> Options'"?
+1, seems like a cleaner answer.
> That's something arbitrarily assigned for all custom GUCs
> and we are sure that none of them will exist in
> postgresql.conf.sample. There's also no guarantee that out-of-core
> custom GUCs will include a dot in their name (even if I know that
> maintainers close to the community adopt this convention and are
> rather careful about that).
Actually we do force that, see valid_custom_variable_name().
But I think your idea is better.
regards, tom lane
В списке pgsql-hackers по дате отправления: