proxy about pgsql-http HOT 5 CLOSED

For now, I think by laying the information you want into the environment variables you start up PostgreSQL with: https://curl.haxx.se/docs/manpage.html#ENVIRONMENT

I haven't thought much about what a clean configuration of such things might be for the extension. GUC variables? Yet More Parameters? A JSONB parameter object?

from pgsql-http.

In the meanwhile I implemented it with guc. I think guc is not bad for general runtime configuration of an extension.

from pgsql-http.

I think there are problems with http_proxy settings though an environment variable. I guess it is not always possible to bind this variable to the sql session (JDBC?). With guc, you won't have any restrictions to set this setting through normal sql statements.

Why not wrapping libcurl options to this extension only when user needs it?

You may have a look at pull request #25 .

from pgsql-http.

GUCs in extensions have caused me quite a bit of pain in the past, though in a non-persistent extension like this one, perhaps they wouldn't be so bad. More problematic is the restricted nature: one for proxy, one for this, one for that. There's so many potential options to set! I feel like a key/value approach w/ json might be better.

from pgsql-http.

See #44 for a maybe solution?

from pgsql-http.