On 08/18/11 2:17 AM, tamanna madaan wrote:
Yes , restarting the slon resolves the issue. But. there are other processes also in my application which connect to postgres . Those processes can also cause "idle in transaction" postgres connection . So, I was wondering if I can make use of tcp_keepalives_idle , tcp_keepalives_interval and tcp_keepalives_count configurations in postgresql.conf to get rid of this "idle in transaction" process after a certain amount of time . Will this help or not ??
Idle In Transaction means that the process has issued a BEGIN to start a transaction but is sitting there doing nothing. if they stay that way for hours, they block vacuum from freeing any tuples since the start of the oldest transaction.. Long running Idle in Transaction processes generally indicate a error in your program design.
-- john r pierce N 37, W 122 santa cruz ca mid-left coast -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
