Re: "stuck spinlock" - Mailing list pgsql-hackers

From Tom Lane
Subject Re: "stuck spinlock"
Date
Msg-id 3918.1386893087@sss.pgh.pa.us
Whole thread Raw
In response to Re: "stuck spinlock"  (Christophe Pettus <xof@thebuild.com>)
Responses Re: "stuck spinlock"
List pgsql-hackers
Christophe Pettus <xof@thebuild.com> writes:
> On Dec 12, 2013, at 3:18 PM, Tom Lane <tgl@sss.pgh.pa.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.

[ shrug... ]  If you aren't getting a core file for a PANIC, then core
files are disabled.  I take no position on the value of the setting
you mention above, but I will note that pg_ctl can't override a hard
"ulimit -c 0" system-wide setting.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Christophe Pettus
Date:
Subject: Re: "stuck spinlock"
Next
From: Peter Geoghegan
Date:
Subject: Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE