pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: adey <adey11@gmail.com>
To: imad <immaad@gmail.com>
Cc: jose fuenmayor <jafn82@gmail.com>
Cc: Shoaib Mir <shoaibmir@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Issue with processes open for clients
Date: Tue, 14 Nov 2006 12:40:32 +1300
Message-ID: <1c66bda80611131540r1ea7fc7w4a8fb308cfad4d03@mail.gmail.com> (raw)
In-Reply-To: <1f30b80c0611101320g10ed4256g439cf262dcc34e5d@mail.gmail.com>
References: <69f2062a0611091154t6a345360g165dd0e80495bcb7@mail.gmail.com>
	<bf54be870611100312s69fb5710pb726406808e9bb8d@mail.gmail.com>
	<69f2062a0611100509v2ad2c475x30aed66f9610ec66@mail.gmail.com>
	<bf54be870611100515r74236f8eu1da57fa3b647aea3@mail.gmail.com>
	<69f2062a0611101313p3bbdbc2bm437011fb98de1144@mail.gmail.com>
	<1f30b80c0611101320g10ed4256g439cf262dcc34e5d@mail.gmail.com>

Is there not a parameter in Postgres to timeout idle connections?

On 11/11/06, imad <immaad@gmail.com> wrote:
>
> I found it on postgresql archives:
> http://archives.postgresql.org/pgsql-admin/2004-09/msg00261.php
>
> This post was by Tom Lane, I hope this is what you want.
>
> It will time out by itself eventually (order of a couple hours probably
> --- it depends on your TCP stack).  You can try a SIGINT or SIGTERM.
> SIGINT is safe but may or may not cause the backend to quit.  SIGTERM
> will make it quit, but I'm not prepared to guarantee that SIGTERM won't
> have bad side effects.  I'd suggest waiting...
>
>
>
> --Imad
> www.EnterpriseDB.com
>
>
> On 11/11/06, jose fuenmayor <jafn82@gmail.com> wrote:
> > Ok but what can i do with that information?
> >
> > On 11/10/06, Shoaib Mir <shoaibmir@gmail.com> wrote:
> > > Check pg_stat_activity for any queries that are in execution mode,
> where
> > command_query will give you the query and you will also get the process
> ids
> > for them in pg_stat_activity.
> > >
> > >
> > > Thanks,
> > > -------
> > > Shoaib Mir
> > > EnterpriseDB (www.enterprisedb.com)
> > >
> > >
> > > On 11/10/06, jose fuenmayor <jafn82@gmail.com > wrote:
> > > > Hi thanks for the answer, but....
> > > > Is not when the query is executed ,is when the user cancells the
> query
> > or kill the client that he is using when this query has not finished,
> then
> > the process in the server is not killed still there taking resources, it
> > happens with some clients (psql, phpPgAdmin), how can I configurate the
> > firewall to elminate idle connections? will this eliminate all
> conections
> > that are not doing anything?, because in my case the client is killed
> but
> > the process in  the server for that client not and continues taking
> > resources.
> > > > thanks in advance!
> > > >
> > > >
> > > >
> > > > On 11/10/06, Shoaib Mir < shoaibmir@gmail.com> wrote:
> > > > > If you don't need the client connection after query has executed
> then
> > just close that client connection or you can have it set in your
> firewall to
> > kill such idle connections who are not doing anything.
> > > > >
> > > > > Thanks,
> > > > > --------
> > > > > Shoaib Mir
> > > > > EnterpriseDB (www.enterprisedb.com)
> > > > >
> > > > >
> > > > >
> > > > > On 11/10/06, jose fuenmayor < jafn82@gmail.com> wrote:
> > > > > > Hi all , I have a question or a doubt, when I ran psql remotely
> it
> > opens a process on the server, so I issue a query (select count(*) from
> > 80millionsrowstable) then I can see that process taking cpu and mem from
> the
> > server (using top), then I cancel the psql on the client, I expect to
> see
> > that process gone but that is not the case it is still there! and taking
> > resources!.
> > > > > >
> > > > > > When I cancelled the query issued by the client is not supposed
> to
> > eliminate the process open for him on the server?
> > > > > >
> > > > > > The process stays hanging there?
> > > > > > why is that?.
> > > > > > Is there any parameter on postgresql or the operating system
> that
> > can tune?
> > > > > > I am using mandriva linux free 2006
> > > > > > kernel 2.6.12
> > > > > > Postgresql 8.0.8
> > > > > > phpPgAdmin 4.0.1 (running in a web server whit php module 5.0.4)
> > > > > >
> > > > > > Same thing using phpPgAdmin
> > > > > >
> > > > > > Thanks in advance! I really aprecciate your help!
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>

view thread (7+ messages)

Message-ID: <1c66bda80611131540r1ea7fc7w4a8fb308cfad4d03@mail.gmail.com>
Permalink:  ../1c66bda80611131540r1ea7fc7w4a8fb308cfad4d03@mail.gmail.com/
Also on:    postgresql.org/message-id/1c66bda80611131540r1ea7fc7w4a8fb308cfad4d03@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: adey11@gmail.com, immaad@gmail.com, jafn82@gmail.com, shoaibmir@gmail.com
  Subject: Re: Issue with processes open for clients
  In-Reply-To: <1c66bda80611131540r1ea7fc7w4a8fb308cfad4d03@mail.gmail.com>
  References: <69f2062a0611091154t6a345360g165dd0e80495bcb7@mail.gmail.com> <bf54be870611100312s69fb5710pb726406808e9bb8d@mail.gmail.com> <69f2062a0611100509v2ad2c475x30aed66f9610ec66@mail.gmail.com> <bf54be870611100515r74236f8eu1da57fa3b647aea3@mail.gmail.com> <69f2062a0611101313p3bbdbc2bm437011fb98de1144@mail.gmail.com> <1f30b80c0611101320g10ed4256g439cf262dcc34e5d@mail.gmail.com> <1c66bda80611131540r1ea7fc7w4a8fb308cfad4d03@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox