| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Timon <timosha(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: stuck spinlock detected at dynahash.c |
| Date: | 2010-10-07 13:43:06 |
| Message-ID: | 27681.1286458986@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Timon <timosha(at)gmail(dot)com> writes:
> 2010/10/6 Alvaro Herrera <alvherre(at)commandprompt(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Juan Sueiro | 2010-10-07 13:45:31 | PostgreSQL 7.4.16 is creating strange files under /var/lib/pgsql |
| Previous Message | Greg Smith | 2010-10-07 13:42:22 | Re: pg_relation_size / could not open relation with OID # |