Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 3C3952E3EA2 for ; Wed, 6 Feb 2008 05:40:57 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 64328-01-4 for ; Wed, 6 Feb 2008 05:40:46 -0400 (AST) Received: from easy2.in-chemnitz.de (easy2.in-chemnitz.de [88.198.17.232]) by postgresql.org (Postfix) with ESMTP id 156732E3C4B for ; Wed, 6 Feb 2008 05:24:59 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by easy2.in-chemnitz.de (Postfix) with ESMTP id E7DB5B2744 for ; Wed, 6 Feb 2008 10:24:56 +0100 (CET) Received: from easy2.in-chemnitz.de ([127.0.0.1]) by localhost (easy.in-chemnitz.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R1IgejFfRQXy for ; Wed, 6 Feb 2008 10:24:56 +0100 (CET) Received: by easy2.in-chemnitz.de (Postfix, from userid 1013) id D5A69B2675; Wed, 6 Feb 2008 10:24:56 +0100 (CET) Date: Wed, 6 Feb 2008 10:24:56 +0100 From: Tino Schwarze To: pgsql-admin@postgresql.org Subject: Re: Postmasters in sleeping mode Message-ID: <20080206092456.GB16997@easy2.in-chemnitz.de> References: <3D5445983859B84B92669C0D883EA6FB0C23E934@ZENMAILHQ1.ind.zensar.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <3D5445983859B84B92669C0D883EA6FB0C23E934@ZENMAILHQ1.ind.zensar.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/54 X-Sequence-Number: 28128 On Wed, Feb 06, 2008 at 01:20:50PM +0530, Suresh Gupta VG wrote: > I am on Solaris-9 and Pgsql-7.4.2. This database is running on the live > production server. It takes more than 5 minutes to update one single > query. This is very horrible and completely not acceptable on the live. Take one of those slow queries and use "EXPLAIN ANALYZE" to figure out why they are so slow. BTW: Consider upgrading to the latest 7.4 (IIRC 7.4.11) - there should be a lot of bugfixes you are missing, some of which may lead to data corruption. > We had scheduled Vacuum on daily basis at low traffic time of the day. > Due to this, the client application is getting time out and the > particular transaction is getting failed. > > We observed numbers of postmaster processes are running in the sleeping > mode. We also observed some of the processes are running with the > previous dates. The maximum connections configures is 100, but I can see > number of transactions around 200 at some time of the day(May be peak > time of transactions). Pls advice me to get rid of this. > > User Pid PPID Status Time Etime Stime > Command > > -------- ---- ---- ------ --- ---------- -------- > ----------------- > > pgsql 2519 1 S 1:45 30-20:50:51 Jan_06 > /db1/postgresql/bin/postmaster This is just the normal state of any Unix process which currently does nothing (e.g. is waiting for input from somewhere). I'm not sure what Etime and Stime means - I don't know Solaris. The Time column tells you how much CPU time this process has used since it was created. In PostgreSQL you have one postgres process for each connection. So you can see when the connection was opened by looking at the process' creation time. HTH, Tino. -- www.craniosacralzentrum.de www.spiritualdesign-chemnitz.de Tino Schwarze * Lortzingstraße 21 * 09119 Chemnitz