From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
Cc: | Brendan Hill <brendanh(at)jims(dot)net>, 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-07-29 10:18:07 |
Message-ID: | 9837222c0907290318n385e1906oc1fc92c713d9025f@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Jul 29, 2009 at 12:08, Craig Ringer<craig(at)postnewspapers(dot)com(dot)au> wrote:
> Craig Ringer wrote:
>>
>> Brendan Hill wrote:
>>>
>>> Hi Tom,
>>>
>>> Given it's on Windows, any suggestion for how I would get hold of this?
>>> (Process Monitor tool perhaps?)
>>
>> I think you can get stack traces from Process Monitor using "Tools ->
>> Stack Summary". I find it a bit hard to interpret this data, though, and I'm
>> not sure how useful it is for this sort of thing.
>>
>>
>>
>> [ The following instructions may be put on the PostgreSQL wiki as advice
>> for getting debugging details for runaway PostgreSQL processes on Windows if
>> desired ]:
>
> Actually, I've expanded on the instructions and done it. See:
>
> http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Windows
>
> Accessible from "General Articles and Guides" -> "Troubleshooting" ->
> "Generating_a_stack_trace_of_a_PostgreSQL_backend".
This is very useful, thanks for putting it up!
--
Magnus Hagander
Self: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2009-07-29 11:13:47 | Reporting problems wiki article - help requested |
Previous Message | Craig Ringer | 2009-07-29 10:08:56 | Re: Idle processes chewing up CPU? |