Re: pgstat wait timeout (by Robert Schnabel)

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Alexey Luchko <luch(at)ank-sia(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: pgstat wait timeout (by Robert Schnabel)
Date: 2009-12-16 15:55:50
Message-ID: 603c8f070912160755h5c9c4652o9647a02e7cd2dd4c@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Dec 16, 2009 at 10:45 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> On Wed, Dec 16, 2009 at 16:12, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
>>> Alexey Luchko wrote:
>>>> postgres.exe!mdpostckpt+0x181b38
>>>> postgres.exe!mdpostckpt+0x18bbdb
>>
>>> This stack trace seems bogus.  The stats collector should not be calling
>>> mdpostckpt at all.
>>
>> Given the size of the offsets, it's pretty clear that it's not actually
>> in mdpostckpt at all.  Probably this is a stripped executable and
>> mdpostckpt is just the nearest global symbol.
>
> 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 :)

We should really take some of the vast quantity of really useful
information that is in the wiki and try to index it somehow or
incorporate it into the docs. I'm always learning about new pages
that have good stuff on them, but I never seem to stumble across them
organically.

...Robert

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2009-12-16 16:05:58 Re: pgstat wait timeout (by Robert Schnabel)
Previous Message Magnus Hagander 2009-12-16 15:45:13 Re: pgstat wait timeout (by Robert Schnabel)