pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Craig Ringer <craig@postnewspapers.com.au>
To: bakkiya <bakkiya@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: 100% CPU Utilization when we run queries.
Date: Wed, 08 Jun 2011 13:07:10 +0800
Message-ID: <4DEF037E.9020105@postnewspapers.com.au> (raw)
In-Reply-To: <1307506768241-4465765.post@n5.nabble.com>
References: <1307506768241-4465765.post@n5.nabble.com>

On 8/06/2011 12:19 PM, bakkiya wrote:
> We have a postgresql 8.3.8 DB which consumes 100% of the CPU whenever we run
> any query.

Yep, that's what it's supposed to do if it's not I/O limited. What's the 
problem? Is the query taking longer than you think it should to execute? 
Do you expect it to be waiting for disk rather than CPU?

Please show your problem query/queries, and EXPLAIN ANALYZE output. See: 
http://wiki.postgresql.org/wiki/Guide_to_reporting_problems

> http://postgresql.1045698.n5.nabble.com/file/n4465765/untitled.bmp

Heh. That's been resized to a 250x250 bitmap, which isn't exactly useful 
or readable.

Why not paste the text rather than a screenshot?

-- 
Craig Ringer

Tech-related writing at http://soapyfrogs.blogspot.com/



view thread (13+ messages)  latest in thread

Message-ID: <4DEF037E.9020105@postnewspapers.com.au>
Permalink:  ../4DEF037E.9020105@postnewspapers.com.au/
Also on:    postgresql.org/message-id/4DEF037E.9020105@postnewspapers.com.au

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: craig@postnewspapers.com.au, bakkiya@gmail.com
  Subject: Re: 100% CPU Utilization when we run queries.
  In-Reply-To: <4DEF037E.9020105@postnewspapers.com.au>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox