From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | scott(at)deltaex(dot)com |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #14223: stuck spinlock detected at bufmgr.c:1440 |
Date: | 2016-07-01 21:22:15 |
Message-ID: | 20160701212215.dooi5bznalrbc3qa@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hi,
On 2016-07-01 20:22:34 +0000, scott(at)deltaex(dot)com wrote:
> The following bug has been logged on the website:
>
> Bug reference: 14223
> Logged by: Scott Milliken
> Email address: scott(at)deltaex(dot)com
> PostgreSQL version: 9.5.3
> Operating system: Linux 3.2.0-60-generic, Ubuntu 12.04.5 LTS
> Description:
>
> I experienced a PostgreSQL server crash, and thought I'd share the details
> in case it's helpful.
>
> Error message:
> 2016-07-01 10:45:27.155
> PDT,"xxx","xxx",2057,"xxxx:50539",57765b4e.809,80,"INSERT",2016-07-01
> 05:00:14 PDT,8/739892,134888654,PANIC,XX000,"stuck spinlock (0x7f8e1d81e360)
> detected at bufmgr.c:1440",,,,,,"INSERT INTO ...."
Hm. Interesting.
> full_page_writes = off (ZFS guarantees consistency)
I don't believe that's actually true, but it's surely unrelated to this
issue.
> This query has run hundreds of thousands of times on this particular
> database successfully; this is the first instance of this error that has
> occured.
Hm. Do you happen to have system statistics (load, user cpu, sys cpu)
available by any chance?
> This issue isn't urgent for me and I have no way to reproduce it, but figure
> it wouldn't hurt to share.
That's helpful!
Andres
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2016-07-01 21:29:07 | Re: BUG #14223: stuck spinlock detected at bufmgr.c:1440 |
Previous Message | scott | 2016-07-01 20:22:34 | BUG #14223: stuck spinlock detected at bufmgr.c:1440 |