Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 54D839F954B for ; Tue, 28 Aug 2007 16:11:59 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 72008-02 for ; Tue, 28 Aug 2007 16:11:43 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from lists.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id 16BAA9F944C for ; Tue, 28 Aug 2007 16:11:44 -0300 (ADT) Received: from perhan.alvh.no-ip.org (201-220-104-109.bk9-dsl.surnet.cl [201.220.104.109]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l7SJBjtJ023854; Tue, 28 Aug 2007 12:11:46 -0700 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 0F6CB47C5F; Tue, 28 Aug 2007 15:11:44 -0400 (CLT) Date: Tue, 28 Aug 2007 15:11:44 -0400 From: Alvaro Herrera To: John R Allgood Cc: Tom Lane , pgsql-admin@postgresql.org Subject: Re: How to monitor resources on Linux. Message-ID: <20070828191143.GE13868@alvh.no-ip.org> References: <46D4353F.2040209@the-allgoods.net> <815.1188324416@sss.pgh.pa.us> <46D470D8.2030605@the-allgoods.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46D470D8.2030605@the-allgoods.net> User-Agent: Mutt/1.5.16 (2007-06-11) X-Virus-Scanned: ClamAV 0.91.1/4087/Tue Aug 28 03:05:35 2007 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Tue, 28 Aug 2007 12:11:46 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/357 X-Sequence-Number: 26688 John R Allgood wrote: > Hey Tom > > Thanks for responding. This issue came around because of a situation > yesterday with processes being killed off by the kernel. I believe my co > worker Geof Myers sent a post yesterday and the response was to adjust the > vm.commit_memory=2. Several time throughout the day we see memory usage > peak and then it will go down. We have multiple postmasters running for > each of our division so that I we have a problem with a database it only > affects that one. It make it diffucult to tune a system with this many > postmasters running. Each database is tuned according to need. We allow > anywhere between 5-50 max connections. So what I am looking for is? Any of work_mem or maintenance_worm_mem set too high can cause excessive memory usage. What do you have these set to? -- Alvaro Herrera http://www.amazon.com/gp/registry/5ZYLFMCVHXC "World domination is proceeding according to plan" (Andrew Morton)