Re: Idle processes chewing up CPU?

From: "Brendan Hill" <brendanh(at)jims(dot)net>
To: "'Craig Ringer'" <craig(at)postnewspapers(dot)com(dot)au>
Cc: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: Idle processes chewing up CPU?
Date: 2009-08-07 01:14:06
Message-ID: 004901ca16fc$5d99a340$18cce9c0$@net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi Craig, the instructions are great. I've gone through them and confirmed
I'm getting the full details in the stack traces. When it happens again,
I'll post the most useful stack traces and we'll be able to look at it
properly. Thanks again for your help so far, the responsiveness is terrific.

-Brendan

-----Original Message-----
From: Craig Ringer [mailto:craig(at)postnewspapers(dot)com(dot)au]
Sent: Wednesday, 5 August 2009 5:44 PM
To: Brendan Hill
Cc: 'Tom Lane'; pgsql-general(at)postgresql(dot)org
Subject: RE: [GENERAL] Idle processes chewing up CPU?

On Wed, 2009-08-05 at 16:44 +1000, Brendan Hill wrote:
> Hi Craig,
>
> Sorry, I had the stack trace so I thought it was enough. I'll make sure
the
> debug environment is set up and post the full stack traces again.

No worries. Sorry it cost you time.

I've extended the wiki article on win32 debug info to (hopefully)
explain how to identify a useful stack trace, or at least a likely bogus
one. If you feel like a look I'd value your opinion especially when it
comes to clarity/readability.

http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQ
L_backend_on_Windows

--
Craig Ringer

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Christine Desmuke 2009-08-07 02:02:49 Re: Make check fails on 8.3.7
Previous Message Josh Trutwin 2009-08-06 22:33:24 Re: Empty Updates, ON UPDATE triggers and Rules