Re: pgstat wait timeout (by Robert Schnabel)

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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:45:13
Message-ID: 9837222c0912160745m95f7f9bk34ed49058b879267@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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 :)

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Haas 2009-12-16 15:55:50 Re: pgstat wait timeout (by Robert Schnabel)
Previous Message Tom Lane 2009-12-16 15:12:55 Re: pgstat wait timeout (by Robert Schnabel)