> On May 3, 2021, at 8:22 AM, Robert Haas <robertmhaas@gmail.com> wrote:
>
> One problem with having a separate predefined role for every PGC_SUSET
> GUC is that it's no help for extensions. Both auto_explain and
> pg_stat_statements have such GUCs, and there may be out-of-core
> extensions that do as well. We should try to come up with a system
> that doesn't leave them out in the cold.
As things stand, all custom variables defined via the DefineCustom{Bool,Int,Real,String,Enum}Variable are placed in the
CUSTOM_OPTIONSconfig_group. We could add a role for controlling any SUSET CUSTOM_OPTIONS GUCs, or we could extend
thosefunctions to take a config_group option, or perhaps some of both. I haven't thought too much yet about whether
allowingextensions to place a custom GUC into one of the predefined groups would be problematic. Any thoughts on that?
—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
