X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 832C89DC863 for ; Tue, 13 Dec 2005 12:40:34 -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 02915-07 for ; Tue, 13 Dec 2005 12:40:33 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mercury.wardbrook.com (host-84-9-98-118.bulldogdsl.com [84.9.98.118]) by postgresql.org (Postfix) with ESMTP id C72159DC872 for ; Tue, 13 Dec 2005 12:40:31 -0400 (AST) Received: from localhost (localhost.localdomain [127.0.0.1]) by mercury.wardbrook.com (Postfix) with ESMTP id AC51B532EB; Tue, 13 Dec 2005 16:37:45 +0000 (GMT) Received: by mercury.wardbrook.com (Postfix, from userid 505) id 7C50D532EF; Tue, 13 Dec 2005 16:37:44 +0000 (GMT) Received: from www.airinformation.com (localhost.localdomain [127.0.0.1]) by mercury.wardbrook.com (Postfix) with SMTP id CEF6D532EB; Tue, 13 Dec 2005 16:37:42 +0000 (GMT) Received: from 195.152.219.3 (SquirrelMail authenticated user johnsw) by mercury.wardbrook.com with HTTP; Tue, 13 Dec 2005 16:37:42 -0000 (GMT) Message-ID: <6597.195.152.219.3.1134491862.squirrel@mercury.wardbrook.com> In-Reply-To: <6375.1134486792@sss.pgh.pa.us> References: <1133891282.11803.7.camel@state.g2switchworks.com> <1133991204.11803.43.camel@state.g2switchworks.com> <6353.1134016733@sss.pgh.pa.us> <439DDB49.3000905@freedomhealthcare.org> <439E7B7A.9080205@wardbrook.com> <3666.1134460063@sss.pgh.pa.us> <439E80B1.8030800@wardbrook.com> <6375.1134486792@sss.pgh.pa.us> Date: Tue, 13 Dec 2005 16:37:42 -0000 (GMT) Subject: Re: Memory Leakage Problem From: "John Sidney-Woollett" To: "Tom Lane" Cc: "John Sidney-Woollett" , "pgsql general" Reply-To: johnsw@wardbrook.com User-Agent: SquirrelMail/1.4.2 [CVS] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal X-Virus-Scanned: by AMaViS 0.3.12 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0 required=5 tests=[none] X-Spam-Score: 0 X-Spam-Level: X-Archive-Number: 200512/646 X-Sequence-Number: 88209 Tom Lane said: > John Sidney-Woollett writes: >> Tom Lane wrote: >>> *What* is consuming memory, exactly --- which processes? > >> Sorry but I don't know how to determine that. > > Try "ps auxw", or some other incantation if you prefer, so long as it > includes some statistics about process memory use. What you showed us > is certainly not helpful. At the moment not one process's VSZ is over 16Mb with the exception of one of the slon processes which is at 66Mb. I'll run this over the next few days and especially as the server starts bogging down to see if it identifies the culprit. Is it possible to grab memory outsize of a processes space? Or would a leak always show up by an ever increasing VSZ amount? Thanks John