On 8/23/2015 10:49 AM, Tom Lane wrote:
However, what this smells like to me is a permissions problem. I think
you were way too quick to dismiss the idea that SELinux (or something
just like it) is restricting outbound internet connections from Postgres.
It's standard for SELinux to be configured so that network-accessible
daemons like Postgres are locked down harder than the very same code
would be treated when being invoked from the command line --- and network
access would be one of the prime candidates to be disabled by default.
Have you poked around under /var/log/ to see if the kernel logs anything
when the connection attempt doesn't work? For that matter, have you
checked the postmaster log to see what Postgres logs about it?
also, `getenforce` ... if it comes back enabled, as root, do...
setenforce permissive
and try your trigger again (don't reboot or restart anything, just do it)
--
john r pierce, recycling bits in santa cruz