Scott Marlowe [scott.marl...@gmail.com] wrote:
Might you have a firewall that's killing the connections? What does
netstat -an on the client side say about these connections?
I don't think so: 1) app and postgres are on the same machine and 2)
this has been the set up for months and I don't think anyone has diddled
with the machine.
netstat -an | fgrep 5432 shows:
[r...@rdl64xeoserv01 log]# netstat -an | fgrep 5432
tcp 0 0 0.0.0.0:5432 0.0.0.0:*
LISTEN
tcp 0 0 127.0.0.1:5432 127.0.0.1:35996
ESTABLISHED
tcp 0 0 127.0.0.1:5432 127.0.0.1:35999
ESTABLISHED
tcp 0 0 127.0.0.1:5432 127.0.0.1:36017
ESTABLISHED
tcp 0 0 127.0.0.1:5432 127.0.0.1:36019
ESTABLISHED
tcp 0 0 127.0.0.1:5432 127.0.0.1:36018
ESTABLISHED
tcp 0 0 127.0.0.1:5432 127.0.0.1:36005
ESTABLISHED
tcp 0 0 127.0.0.1:5432 127.0.0.1:36001
ESTABLISHED
tcp 0 0 127.0.0.1:5432 127.0.0.1:36013
ESTABLISHED
tcp 0 0 127.0.0.1:5432 127.0.0.1:36008
ESTABLISHED
tcp 0 0 127.0.0.1:5432 127.0.0.1:36011
ESTABLISHED
tcp 0 0 130.200.163.80:5432 130.200.164.26:50481
ESTABLISHED
tcp 0 0 :::5432 :::*
LISTEN
tcp 0 0 ::ffff:127.0.0.1:36001 ::ffff:127.0.0.1:5432
ESTABLISHED
tcp 0 0 ::ffff:127.0.0.1:36005 ::ffff:127.0.0.1:5432
ESTABLISHED
tcp 0 0 ::ffff:127.0.0.1:36008 ::ffff:127.0.0.1:5432
ESTABLISHED
tcp 0 0 ::ffff:127.0.0.1:36011 ::ffff:127.0.0.1:5432
ESTABLISHED
tcp 0 0 ::ffff:127.0.0.1:36013 ::ffff:127.0.0.1:5432
ESTABLISHED
tcp 0 0 ::ffff:127.0.0.1:36017 ::ffff:127.0.0.1:5432
ESTABLISHED
tcp 0 0 ::ffff:127.0.0.1:36019 ::ffff:127.0.0.1:5432
ESTABLISHED
tcp 0 0 ::ffff:127.0.0.1:36018 ::ffff:127.0.0.1:5432
ESTABLISHED
tcp 0 0 ::ffff:127.0.0.1:35996 ::ffff:127.0.0.1:5432
ESTABLISHED
tcp 0 0 ::ffff:127.0.0.1:35999 ::ffff:127.0.0.1:5432
ESTABLISHED
unix 2 [ ACC ] STREAM LISTENING 2640437 /tmp/.s.PGSQL.5432
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
