X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 83DCD40C05B for ; Sun, 30 Jan 2005 03:21:19 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 86579-06 for ; Sun, 30 Jan 2005 03:21:00 +0000 (GMT) Received: from rediffmail.com (unknown [203.199.83.37]) by svr1.postgresql.org (Postfix) with SMTP id C9D9F40C063 for ; Sun, 30 Jan 2005 03:17:59 +0000 (GMT) Received: (qmail 27719 invoked by uid 510); 30 Jan 2005 03:19:34 -0000 Date: 30 Jan 2005 03:19:34 -0000 Message-ID: <20050130031934.27718.qmail@webmail27.rediffmail.com> Received: from unknown (202.88.246.13) by rediffmail.com via HTTP; 30 jan 2005 03:19:33 -0000 MIME-Version: 1.0 From: "N S" Reply-To: "N S" To: pgsql-performance@postgresql.org Subject: Re: Postgres server getting slow!! Content-type: multipart/alternative; boundary="Next_1107055173---0-203.199.83.37-27702" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.71 tagged_above=0 required=5 tests=DNS_FROM_RFC_ABUSE, HTML_30_40, HTML_IMAGE_ONLY_16, HTML_MESSAGE, MSGID_FROM_MTA_HEADER X-Spam-Level: * X-Archive-Number: 200501/619 X-Sequence-Number: 10309 This is a multipart mime message --Next_1107055173---0-203.199.83.37-27702 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline =0A=0AThanks tom. I checked the client side software. The software closes= connection when connected locally. But when connected through dialup,=0Ath= is problem comes. I will check the ppp connection also.=0AIs there any meth= od of killing old pids. And also any performance tuning to be done on postg= resql.conf file.=0A=0AThe database now contains 20K records. Will that caus= e a problem?=0A=0ARegds=0A=0ANarayanan=0A=0AOn Sat, 29 Jan 2005 Tom Lane w= rote :=0A>"Narayanan Subramaniam Iyer" writes:=0A> >= 1) When 3 or 4 clients connect to this server, the pids are created and=0A= > > those pids are not killed even after the client disconnects.=0A>=0A>In = that case your clients are not really disconnecting. Take a closer=0A>look= at your client-side software.=0A>=0A> regards, tom lane=0A>=0A>--------= -------------------(end of broadcast)---------------------------=0A>TIP 3: = if posting/reading through Usenet, please send an appropriate=0A> sub= scribe-nomail command to majordomo@postgresql.org so that your=0A> me= ssage can get through to the mailing list cleanly=0A --Next_1107055173---0-203.199.83.37-27702 Content-type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline

=0A 
=0A
=0AThanks tom. I checked the client side software. = The software closes connection when connected locally. But when connected t= hrough dialup,
=0Athis problem comes. I will check the ppp connection al= so.
=0AIs there any method of killing old pids. And also any performance= tuning to be done on postgresql.conf file.
=0A
=0AThe database now c= ontains 20K records. Will that cause  a problem?
=0A
=0ARegds=0A
=0ANarayanan
=0A
=0AOn Sat, 29 Jan 2005 Tom Lane wrote :
= =0A>"Narayanan Subramaniam Iyer" <bunix@rediffmail.com> = writes:
=0A> > 1) When 3 or 4 clients connect to this server, the = pids are created and
=0A> > those pids are not killed even after t= he client disconnects.
=0A>
=0A>In that case your clients are n= ot really disconnecting.  Take a closer
=0A>look at your client-= side software.
=0A>
=0A>          &nbs= p;     regards, tom lane
=0A>
=0A>--------------= -------------(end of broadcast)---------------------------
=0A>TIP 3:= if posting/reading through Usenet, please send an appropriate
=0A>&n= bsp;     subscribe-nomail command to majordomo@postgresql.org so= that your
=0A>      message can get through to the m= ailing list cleanly
=0A=0A

=0A

=0A=0A --Next_1107055173---0-203.199.83.37-27702--