Bookmarks

Yahoo Gmail Google Facebook Delicious Twitter Reddit Stumpleupon Myspace Digg

Search queries

sqldatasource dal, wwwxxxenden, convert raid5 to raid 10 mdadm, apache force chunked, nrao wwwxxx, xxxxxdup, procmail change subject header, wwwXxx not20, Wwwxxx.doks sas, linux raid resync after reboot

Links

XODOX
Impressum

#1: "idle in transaction" postgres connection

Posted on 2011-08-18 11:34:25 by tamanna madaan

--20cf3040e9c6973fab04aac4510b
Content-Type: text/plain; charset=ISO-8859-1

Hi All

I 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 transaction

I wonder what could have lead to that hung postgres process . I googled
about it a lot and they say that it could be
because of abrupt netwotk issue between slony and postgres . But in my case
slon was connected
to its local postgres database. So, network wont be an issue in this case .
Restarting the slon/postgres resolves
the issue. But, there are other processes also in my application which
connect to postgres using psqlODBC . Those
processes can also cause "idle in transaction" postgres connection . I can't
afford restarting any of the processes
to resolve this issue. 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" processes
after a certain amount of time . Will this help or not ??


Thanks...
Tamanna

--20cf3040e9c6973fab04aac4510b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p><br clear=3D"all">Hi All</p>
<p>I am using postgres-8.4.0 on a cluster setup with slony-2.0.4 being used=
for replication. <br>Recently , I saw a &quot;idle in transaction&quot; po=
stgres process as below.<br>=A0<br>postgres 13052 14742 0 May13 ? 00:00:00 =
postgres: slon abc 172.16.1.1(49017) idle in transaction</p>

<p>I wonder what could have lead to that hung postgres process . I googled =
about it a lot and they say that it could be <br>because of abrupt netwotk =
issue between slony and postgres . But in my case slon was connected<br>
to its local postgres database. So, network wont be an issue in this case .=
Restarting the slon/postgres resolves <br>the issue. But, there are other =
processes also in my application=A0 which connect to postgres using psqlODB=
C . Those <br>
processes can also cause &quot;idle in transaction&quot; postgres connectio=
n . I can&#39;t afford restarting any of the processes<br>to resolve this i=
ssue. So, I was wondering if I can make use of tcp_keepalives_idle , tcp_ke=
epalives_interval and <br>
tcp_keepalives_count configurations in postgresql.conf to get rid of this &=
quot;idle in transaction&quot; processes <br>after a certain amount of time=
. Will this help or not ??</p>
<p><br>Thanks...<br>Tamanna</p>
<p>=A0</p>

--20cf3040e9c6973fab04aac4510b--

Report this message

#2: Re: "idle in transaction" postgres connection

Posted on 2011-08-22 06:51:20 by tamanna madaan

--20cf303dd7868ae3b404ab10d435
Content-Type: text/plain; charset=ISO-8859-1

Can anyone please suggest me on this .


Thanks..
Tamanna

On Thu, Aug 18, 2011 at 3:04 PM, tamanna madaan <
tamanna.madaan@globallogic.com> wrote:

>
> Hi All
>
> I 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 transaction
>
> I wonder what could have lead to that hung postgres process . I googled
> about it a lot and they say that it could be
> because of abrupt netwotk issue between slony and postgres . But in my case
> slon was connected
> to its local postgres database. So, network wont be an issue in this case .
> Restarting the slon/postgres resolves
> the issue. But, there are other processes also in my application which
> connect to postgres using psqlODBC . Those
> processes can also cause "idle in transaction" postgres connection . I
> can't afford restarting any of the processes
> to resolve this issue. 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" processes
> after a certain amount of time . Will this help or not ??
>
>
> Thanks...
> 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

--20cf303dd7868ae3b404ab10d435
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Can anyone please suggest me on this .<br><br><br>Thanks..<br>Tamanna<br><b=
r><div class=3D"gmail_quote">On Thu, Aug 18, 2011 at 3:04 PM, tamanna madaa=
n <span dir=3D"ltr">&lt;<a href=3D"mailto:tamanna.madaan@globallogic.com">t=
amanna.madaan@globallogic.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><p><br clear=3D"a=
ll">Hi All</p>
<p>I am using postgres-8.4.0 on a cluster setup with slony-2.0.4 being used=
for replication. <br>Recently , I saw a &quot;idle in transaction&quot; po=
stgres process as below.<br>=A0<br>postgres 13052 14742 0 May13 ? 00:00:00 =
postgres: slon abc 172.16.1.1(49017) idle in transaction</p>


<p>I wonder what could have lead to that hung postgres process . I googled =
about it a lot and they say that it could be <br>because of abrupt netwotk =
issue between slony and postgres . But in my case slon was connected<br>

to its local postgres database. So, network wont be an issue in this case .=
Restarting the slon/postgres resolves <br>the issue. But, there are other =
processes also in my application=A0 which connect to postgres using psqlODB=
C . Those <br>

processes can also cause &quot;idle in transaction&quot; postgres connectio=
n . I can&#39;t afford restarting any of the processes<br>to resolve this i=
ssue. So, I was wondering if I can make use of tcp_keepalives_idle , tcp_ke=
epalives_interval and <br>

tcp_keepalives_count configurations in postgresql.conf to get rid of this &=
quot;idle in transaction&quot; processes <br>after a certain amount of time=
. Will this help or not ??</p>
<p><br>Thanks...<br><font color=3D"#888888">Tamanna</font></p>
<p>=A0</p>
</blockquote></div><br><br clear=3D"all"><br>-- <br>Tamanna Madaan | Associ=
ate Consultant | GlobalLogic Inc.<br>Leaders in Software R&amp;D Services<b=
r>ARGENTINA | CHILE | CHINA | GERMANY | INDIA | ISRAEL | UKRAINE | UK | USA=
<br>
<br>Office: +0-120-406-2000 x 2971 <br><br><a href=3D"http://www.globallogi=
c.com" target=3D"_blank">www.globallogic.com</a><br><br><br>

--20cf303dd7868ae3b404ab10d435--

Report this message