| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Denis Perchine <dyp(at)perchine(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Quite strange crash |
| Date: | 2001-01-08 15:53:20 |
| Message-ID: | 17800.978969200@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Denis Perchine <dyp(at)perchine(dot)com> writes:
> On Monday 08 January 2001 00:08, Tom Lane wrote:
>>>> FATAL: s_lock(401f7435) at bufmgr.c:2350, stuck spinlock. Aborting.
>>
>> Were there any errors before that?
> No... Just clean log (I redirect log from stderr/out t file, and all
> other to syslog).
The error messages would be in the syslog then, not in stderr.
> And the last query was:
> Jan 7 04:27:53 mx postgres[1008]: query: select message_id from pop3 where
> server_id = 22615
How about the prior queries of other processes? Keep in mind that the
spinlock could have been left locked by any backend, not only the one
that complained about it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | The Hermit Hacker | 2001-01-08 15:55:10 | Re: heap_update is broken in current sources |
| Previous Message | Tom Lane | 2001-01-08 15:32:16 | Re: pg_dump return status.. |