Hi
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 ??
Thanks...
Tamanna
On Tue, Aug 16, 2011 at 11:56 AM, Abbas <abbas.dba@xxxxxxxxx> wrote:
Best Regards,
Abbas
On Mon, Aug 15, 2011 at 11:14 PM, tamanna madaan <tamanna.madaan@xxxxxxxxxxxxxxx> wrote:
Hi AllI am using postgres-8.4.0 on a cluster setup with slony-2.0.4 being used for replication.Recently , I saw a "idle in transaction" postgres process as below.postgres 13052 14742 0 May13 ? 00:00:00 postgres: slon abc 172.16.1.1(49017) idle in transactionI wonder what could have lead to that hung postgres process . I googled about it a lot and they say that it could bebecause of abrupt netwotk issue between slony and postgres . But in my case slon was connectedto its local postgres database. So, network wont be an issue in this case . What else could be the reason forthis hung process ? What should I do to come over this kind of issue in future. I think this hung process would havetaken locks on various tables. I wonder if killing the "idle in transaction" process would cause the locks on the tablesto be released or not. Can anyone please help me on that.Of course it is a slon process if it is not due to a network issue, then might be any of your scripts, if not you can try by restarting the slon process on origin.
Abbas.Thanks in Advance .Tamanna
--
Tamanna Madaan | Associate Consultant | GlobalLogic Inc.
Leaders in Software R&D Services
ARGENTINA | CHILE | CHINA | GERMANY | INDIA | ISRAEL | UKRAINE | UK | USA
Office: +0-120-406-2000 x 2971
www.globallogic.com
