Re: stuck spinlock detected at dynahash.c - Mailing list pgsql-general

From Tom Lane
Subject Re: stuck spinlock detected at dynahash.c
Date
Msg-id 27681.1286458986@sss.pgh.pa.us
Whole thread Raw
In response to Re: stuck spinlock detected at dynahash.c  (Timon <timosha@gmail.com>)
List pgsql-general
Timon <timosha@gmail.com> writes:
> 2010/10/6 Alvaro Herrera <alvherre@commandprompt.com>:
>>> WARNING: �pgstat wait timeout
>>> WARNING: �pgstat wait timeout
>>> PANIC: �stuck spinlock (0x7fd877761af8) detected at dynahash.c:981
>>> PANIC: �stuck spinlock (0x7fd877761af8) detected at dynahash.c:981
>>
>> What platform is this? �Are you running on some sort of virtualized
>> system?

> no, simple dedicated server with Linux Fedora 13 x86_64
> kernel-2.6.33.6-147.2.4.fc13.x86_64

There's not a lot we can do with only this much information.  I'd
suggest running the postmaster with core dumps enabled (ulimit -c
unlimited) so that if it happens again, the PANICs will result in
core dumps that you can get stack traces from.

            regards, tom lane

pgsql-general by date:

Previous
From: Greg Smith
Date:
Subject: Re: pg_relation_size / could not open relation with OID #
Next
From: Juan Sueiro
Date:
Subject: PostgreSQL 7.4.16 is creating strange files under /var/lib/pgsql