> This patch suggests context independent API for managing extension > defined sets of options. It is used for > relation options and similar options, but cat be also used for any > options sets, may be with small modifications. > > GUC options are almost same options as relation options. That is why, I > guess, Alvaro suggested you to look at this patch.
Yes, but wouldn't that still require a generic refactoring of GUCs? I'm not saying that would be a bad thing, but that's a big task in itself. But if I think about it in the general context of this thread (adding extension options to pg_hba, ignoring the part that I tried to implement it with GUCs in the current patch), that can be related. Thanks for the clarification, I'll look into it in more detail.
