Re: pgstat wait timeout (by Robert Schnabel)

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: pgstat wait timeout (by Robert Schnabel)
Дата
Msg-id 603c8f070912160755h5c9c4652o9647a02e7cd2dd4c@mail.gmail.com
обсуждение исходный текст
Ответ на Re: pgstat wait timeout (by Robert Schnabel)  (Magnus Hagander <magnus@hagander.net>)
Ответы Re: pgstat wait timeout (by Robert Schnabel)  (Alvaro Herrera <alvherre@commandprompt.com>)
Re: pgstat wait timeout (by Robert Schnabel)  (Craig Ringer <craig@postnewspapers.com.au>)
Список pgsql-bugs
On Wed, Dec 16, 2009 at 10:45 AM, Magnus Hagander <magnus@hagander.net> wro=
te:
> On Wed, Dec 16, 2009 at 16:12, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Alvaro Herrera <alvherre@commandprompt.com> writes:
>>> Alexey Luchko wrote:
>>>> postgres.exe!mdpostckpt+0x181b38
>>>> postgres.exe!mdpostckpt+0x18bbdb
>>
>>> This stack trace seems bogus. =A0The stats collector should not be call=
ing
>>> mdpostckpt at all.
>>
>> Given the size of the offsets, it's pretty clear that it's not actually
>> in mdpostckpt at all. =A0Probably 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_Postgr=
eSQL_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

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Magnus Hagander
Дата:
Сообщение: Re: pgstat wait timeout (by Robert Schnabel)
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: pgstat wait timeout (by Robert Schnabel)