Re: 003_check_guc.pl crashes if some extensions were loaded.
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: "Anton A. Melnikov" <a.melnikov@postgrespro.ru>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-11-01T23:29:51Z
Lists: 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
Commits
-
Fix 003_check_guc.pl when loading modules with custom GUCs
- 2001aab86099 15.5 landed
- e22819a74736 16.1 landed
- 40d5e5981cc0 17.0 landed