| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Christophe Pettus <xof(at)thebuild(dot)com> |
| Cc: | PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: "stuck spinlock" |
| Date: | 2013-12-13 00:04:47 |
| Message-ID: | 3918.1386893087@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Christophe Pettus <xof(at)thebuild(dot)com> writes:
> 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.
[ 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2013-12-13 00:18:33 | Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE |
| Previous Message | Christophe Pettus | 2013-12-12 23:53:37 | Re: "stuck spinlock" |