Skip site navigation (1) Skip section navigation (2)

Re: BUG #5990: 100% CPU reached

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: Allen Sooredoo <allen_sooredoo(at)carrefour(dot)com>,pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5990: 100% CPU reached
Date: 2011-04-21 01:34:08
Message-ID: 20110421013408.GB4548@tamriel.snowman.net (view raw or flat)
Thread:
Lists: pgsql-bugs
* Kevin Grittner (Kevin(dot)Grittner(at)wicourts(dot)gov) wrote:
> > Could you please provide us some support regarding this issue?
[...]
> Please read this and post to the pgsql-performance list:
>  
> http://wiki.postgresql.org/wiki/SlowQueryQuestions

If that looks like a lot of complication/effort, let's at least start
with including what the hardware is (how much memory, how many CPUs,
what disk configuration, etc) and your postgresql.conf.  The defaults
for postgresql.conf are almost always wrong for a given hardware (unless
you're running on a Celeron w/ 1G of RAM...).

	Thanks,

		Stephen

In response to

pgsql-bugs by date

Next:From: RakshitDate: 2011-04-21 07:17:41
Subject: BUG #5992: The database cluster initialisation failed
Previous:From: Tom LaneDate: 2011-04-20 23:13:25
Subject: Re: BUG #5988: CTINE duplicates constraints

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group