From: | Aldo Sarmiento <aldo(at)bigpurpledot(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Charlin Barak <charlinbarak(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: https call in PostgreSQL |
Date: | 2018-05-11 18:50:05 |
Message-ID: | CAHX=r6yKo1EjVcL0dLU-gNqFmFA=Tk_iJWFggya-+Cy69rV0Bw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Is it acceptable practice to make http calls from DB in most cases? I'm
assuming if the http service becomes unavailable it could clog up all
connections in pg.
I would think adding jobs to some sort of a worker would be a good solution
for most applications.
*Aldo Sarmiento*
On Fri, May 11, 2018 at 11:25 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Charlin Barak <charlinbarak(at)gmail(dot)com> writes:
> > In Oracle, we use the UTL_HTTP package to make a https call within the
> > database. Is there an equivalent in PostgreSQL?
>
> What I'd suggest is using one of the untrusted PLs --- probably plperlu
> or plpythonu --- and coding whatever you need in that language. Once
> you're into one of those languages you have access to all the library
> packages that are installed for it on the server machine, so it shouldn't
> take very much code.
>
> regards, tom lane
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-05-11 18:54:18 | Re: https call in PostgreSQL |
Previous Message | Tom Lane | 2018-05-11 18:25:39 | Re: https call in PostgreSQL |