Re: pgstat wait timeout (by Robert Schnabel)

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Alexey Luchko <luch(at)ank-sia(dot)com>
Cc: pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: pgstat wait timeout (by Robert Schnabel)
Date: 2009-12-16 21:03:48
Message-ID: 9837222c0912161303g17ee2d11vd968561782a9ada5@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Dec 16, 2009 at 17:43, Alexey Luchko <luch(at)ank-sia(dot)com> wrote:
> On 16-12-2009 17:45, Magnus Hagander wrote:
>>
>> If that is so, the OP should follow:
>>
>> http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Windows
>>
>> specifically the part about symbols.
>>
>> Which it certainly looks like :)
>
> How can I find the stats collector's process?

Process explorer will let you see a Mutex named with a description of
the process. Try that.

> Note. The problem appeared in a production system.
> It's preferably not to install lot's of additional software.

The symbols aren't additional software, they are a part of postgresql.

Something like process explorer or windbg is necessary though (but
it's from microsoft, if that helps), because Windows doesn't ship with
any usable debugging tools.

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2009-12-16 21:12:39 Re: BUG #5246: Misleading/inconsistent SQLSTATE behavior
Previous Message Chris Travers 2009-12-16 20:48:20 Re: BUG #5246: Misleading/inconsistent SQLSTATE behavior