Re: high user cpu, massive SELECTs, no io waiting problem - Mailing list pgsql-performance

From Justin Pitts
Subject Re: high user cpu, massive SELECTs, no io waiting problem
Date
Msg-id AANLkTi=mYVFE7QYfrTskUMuJXO34wbzY=1SNi+qgbUhf@mail.gmail.com
Whole thread Raw
In response to Re: high user cpu, massive SELECTs, no io waiting problem  (Greg Smith <greg@2ndquadrant.com>)
List pgsql-performance
I think adding

UNION ALL SELECT 'postgres version', version();

might be a good thing.

On Wed, Feb 16, 2011 at 9:55 AM, Greg Smith <greg@2ndquadrant.com> wrote:
> Kevin Grittner wrote:
>>
>> In fact, I wonder whether we shouldn't leave a couple items you've
>> excluded, since they are sometimes germane to problems posted, like
>> lc_collate and TimeZone.
>
> I pulled some of them out only because they're not really postgresql.conf
> settings; lc_collate and lc_ctype for example are set at initdb time.  Feel
> free to hack on that example if you feel it could be improved, just be aware
> which of those things are not really in the main config file when pondering
> if they should be included.
>
> --
> Greg Smith   2ndQuadrant US    greg@2ndQuadrant.com   Baltimore, MD
> PostgreSQL Training, Services, and 24x7 Support  www.2ndQuadrant.us
> "PostgreSQL 9.0 High Performance": http://www.2ndQuadrant.com/books
>
>
> --
> Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-performance
>

pgsql-performance by date:

Previous
From: bricklen
Date:
Subject: Re: application of KNN code to US zipcode searches?
Next
From: "Strange, John W"
Date:
Subject: Re: high user cpu, massive SELECTs, no io waiting problem