From: | Christophe Pettus <xof(at)thebuild(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: "stuck spinlock" |
Date: | 2013-12-12 23:53:37 |
Message-ID: | 51576D5C-355E-4886-BC4C-33080E1291AC@thebuild.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Dec 12, 2013, at 3:18 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Hm, a PANIC really ought to result in a core file. You sure you don't
> have that disabled (perhaps via a ulimit setting)?
Since it's using the Ubuntu packaging, we have pg_ctl_options = '-c' in /etc/postgresql/9.3/main/pg_ctl.conf.
> As for the root cause, it's hard to say. The file/line number says it's
> a buffer header lock that's stuck. I rechecked all the places that lock
> buffer headers, and all of them have very short code paths to the
> corresponding unlock, so there's no obvious explanation how this could
> happen.
The server was running with shared_buffers=100GB, but the problem has reoccurred now with shared_buffers=16GB.
--
-- Christophe Pettus
xof(at)thebuild(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2013-12-13 00:04:47 | Re: "stuck spinlock" |
Previous Message | Christophe Pettus | 2013-12-12 23:52:22 | Re: "stuck spinlock" |