From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
---|---|
To: | Brendan Hill <brendanh(at)jims(dot)net> |
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-07-29 10:08:56 |
Message-ID: | 4A701FB8.8010306@postnewspapers.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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".
It'd be rather helpful if others could fill in the equivalent for gdb on
Linux/bsd/other unix as linked to here:
http://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
--
Craig Ringer
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2009-07-29 10:18:07 | Re: Idle processes chewing up CPU? |
Previous Message | mukeshp | 2009-07-29 08:53:29 | Re: Monitoring tools for Postgresql |