Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 98F079FBC9F for ; Thu, 22 Mar 2007 15:23:57 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 27744-01-7 for ; Thu, 22 Mar 2007 15:23:48 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from mx1.bandwidth.com (nat0.bandwidth.com [216.27.14.90]) by postgresql.org (Postfix) with SMTP id BCDEC9FBC54 for ; Thu, 22 Mar 2007 15:23:47 -0300 (ADT) Received: (qmail 10025 invoked by uid 1008); 22 Mar 2007 18:23:59 -0000 Received: from dbrain@bandwidth.com by mx1 by uid 1002 with qmail-scanner-1.20 (spamassassin: 2.63. Clear:RC:1(10.1.53.112):. Processed in 0.018944 secs); 22 Mar 2007 18:23:59 -0000 Received: from unknown (HELO ?10.1.53.112?) (10.1.53.112) by mx1.bandwidth.com with SMTP; 22 Mar 2007 18:23:59 -0000 Message-ID: <4602C8FC.7050501@bandwidth.com> Date: Thu, 22 Mar 2007 14:20:44 -0400 From: David Brain User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Bill Moran CC: pgsql-performance@postgresql.org Subject: Re: Potential memory usage issue [resolved] References: <460271B9.8050600@bandwidth.com> <20070322085037.54780906.wmoran@collaborativefusion.com> <46027F65.9080909@bandwidth.com> <20070322091700.9d1553e6.wmoran@collaborativefusion.com> <4602AF1E.8000601@bandwidth.com> <20070322130335.e142faed.wmoran@collaborativefusion.com> In-Reply-To: <20070322130335.e142faed.wmoran@collaborativefusion.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/349 X-Sequence-Number: 23754 Thanks Bill for the explanation - that really helped me out considerably. What this showed me was that there were only 1024 buffers configured. I'm not quite clear as to how this happened as the postgresql.conf files on both systems have the shared_buffers set to ~50000. However it looks as though the system start script was passing in -B 1024 to postmaster which was overriding the postgresql.conf settings. The really odd thing is that that the db start script is also the same on both systems, so there some other difference there that I need to track down. However removing the -B 1024 allowed the settings to revert to the file specified values. So now I'm back to using ~50k buffers again and things are running a little more swiftly, and according to pg_buffercache I'm using 49151 of them (-: Thanks again to those who helped me track this down. David. -- David Brain - bandwidth.com dbrain@bandwidth.com