From: Alan Hodgson <ahodgson@simkin.ca>
Organization: Simkin Network Consulting
To: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL performance issues
Date: Wed, 30 Aug 2006 09:24:26 -0700
User-Agent: KMail/1.9.1
References: <44F446B2.2090900@studentvillage.co.za>
	<9A079B52-0D1D-4682-A841-AA856439698E@infogears.com>
	<44F56CE9.6060602@studentvillage.co.za>
In-Reply-To: <44F56CE9.6060602@studentvillage.co.za>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200608300924.26151@hal.medialogik.com>

On Wednesday 30 August 2006 03:48, Willo van der Merwe 
<willo@studentvillage.co.za> wrote:
> Hi Rusty,
>
> Good ideas and I've implemented some of them, and gained about 10%. I'm
> still sitting on a load avg of about 60.
>
> Any ideas on optimizations on my postgresql.conf, that might have an
> effect?

If all of those sessions are truly doing a select count(*) from a .75 
million row table (plus half a million dead rows), then I'm not suprised 
it's bogged down.  Every query has to loop through the cache of the full 
table in memory every time it's run.

Your CPU is doing something.   I doubt that postgresql.conf settings are  
going to help.  What exactly are all those high CPU usage sessions doing?

-- 
"Government big enough to supply everything you need is big enough to take
everything you have ... the course of history shows that as a government
grows, liberty decreases." -- Thomas Jefferson