X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 68E0B9DC819 for ; Tue, 13 Dec 2005 15:10:24 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 90988-01 for ; Tue, 13 Dec 2005 15:10:19 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id F29599DC81E for ; Tue, 13 Dec 2005 15:10:16 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id jBDJABWm009264; Tue, 13 Dec 2005 14:10:11 -0500 (EST) To: Ameet Kini cc: pgsql-admin@postgresql.org Subject: Re: Lots of postmaster processes In-reply-to: References: <8641.1134497889@sss.pgh.pa.us> Comments: In-reply-to Ameet Kini message dated "Tue, 13 Dec 2005 12:43:34 -0600" Date: Tue, 13 Dec 2005 14:10:11 -0500 Message-ID: <9263.1134501011@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.003 required=5 tests=[AWL=0.003] X-Spam-Score: 0.003 X-Spam-Level: X-Archive-Number: 200512/111 X-Sequence-Number: 19831 Ameet Kini writes: > We're running on tao linux. And yes, there are many client connection > requests sent to the server at the same time. My impression was that > client connection requests usually show up as a postgres process not > postmaster but I could be wrong. Is it that the postmaster forks off a > process on receiving a client connection request and then renames the > process to postgres and I'm issuing my ps command while its in the > intermediate state when its still called postmaster? A bit hard to believe, unless there's something delaying the subprocesses from reaching their first set_ps_display() call. Offhand it looks like DNS problems could cause that (especially if you've got log_hostname enabled), or broken client code that doesn't send the whole startup packet immediately. However, a backend that's hung up that early in the startup process really shouldn't be consuming noticeable resources, so I'm not sure why this would create a performance issue for you. regards, tom lane