keepalive

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,
this weekend our DB server crashed ( 7.4.x ) and the DB engine was relocated
on another server. So far so well.

Unfortunatelly most of our clients are still on a "recv" trying to
recv data from the old DB engine instance:

# netstat -anp | grep ESTABLISHED | grep 54497
tcp 0 0 193.251.135.46:54497 10.10.50.47:5432 ESTABLISHED 27331/psql

# ps -eafwww | grep 27331
apache 27331 27327 0 May13 ? 00:00:00 psql -t -c SELECT is_authorized_flag FROM v_ts_quota WHERE login='*****' -h x.y.z.w xxxx yyyyyyy

as you can see this connection is there since 3 days now.

Digging on it I see these sockets are not using the keepalive options:

netstat -anop | grep ESTABLISHED | grep 54497
tcp 0 0 193.251.135.46:54497 10.10.50.47:5432 ESTABLISHED 27331/psql off (0.00/0/0)

normaly on other connections I see:

tcp 0 0 127.0.0.1:199 127.0.0.1:32784 ESTABLISHED 1255/snmpd keepalive (7102.52/0/0)

The same happens with JDBC connections ( the keepalive missing ).

There is a reason for this or a way to instruct psql to use the keepalive option ?

Regards
Gaetano Mendola

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCiJNF7UpzwH2SGd4RAh8aAJ0WOBEzzjYf1gj1OaFGsFBE9mr4hgCfUhna
D1F420Pa94lvrA04xA73tiE=
=muzn
-----END PGP SIGNATURE-----