| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | John R Pierce <pierce(at)hogranch(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Problem with pl/python procedure connecting to the internet |
| Date: | 2015-08-21 13:48:58 |
| Message-ID: | 55D72C4A.30008@aklaver.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 08/21/2015 12:34 AM, John R Pierce wrote:
> listen_addresses should only affect the interfaces that the postgres
> server is listening to connections from. as long as your app is on the
> same machine, and uses localhost:someport to connect to the postgres
> server, then the default listen_addresses='localhost' should be
> sufficient.'
>
> if you want clients to connect from other systems, then listen_addresses
> = '*' is appropriate.
>
> listen_addresses should have no impact on what your plpython app can
> connect to outside of postgres, unless you're running the 'safe' version
> of pl***
There is no safe(trusted) version of plpython, it is only available as
plpythonu(ntrusted). So you are allowed to run with scissors:)
>
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Igor Sosa Mayor | 2015-08-21 15:28:02 | Re: Problem with pl/python procedure connecting to the internet |
| Previous Message | Adrian Klaver | 2015-08-21 13:44:06 | Re: Problem with pl/python procedure connecting to the internet |