You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It should be possible to just have GUC variables for all the CURL opts we want to support. This wouldn't allow arbitrary CURL option setting, as only options we allowed in the code would be available.
It would then be possible to persist option setting over multiple sessions:
alter database http set http.fooBar = 126;
Note that the GUC names are case insensitive, so that quirk is automatically handled for us too. Kind of wish I had done this to start with.
The text was updated successfully, but these errors were encountered:
The GUC system doesn't require the variable names to be preconfigured if they are under a prefix, so the following works:
In combination with this PostgreSQL function
It should be possible to just have GUC variables for all the CURL opts we want to support. This wouldn't allow arbitrary CURL option setting, as only options we allowed in the code would be available.
It would then be possible to persist option setting over multiple sessions:
Note that the GUC names are case insensitive, so that quirk is automatically handled for us too. Kind of wish I had done this to start with.
The text was updated successfully, but these errors were encountered: