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
