Re: signal 11 segfaults with parallel workers

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Rick Otten <rottenwindfish(at)gmail(dot)com>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: signal 11 segfaults with parallel workers
Date: 2017-07-26 15:43:22
Message-ID: 9144.1501083802@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Rick Otten <rottenwindfish(at)gmail(dot)com> writes:
> I don't have any core files. I suppose that is something I have to enable
> specifically? I'm game to turn it on in case we core dump again.

If you're not seeing core files, you probably need to take measures
to make the postmaster run with "ulimit -c unlimited". It's fairly
common for daemon processes to get launched under "ulimit -c 0"
by default, for largely-misguided-imo security reasons.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Rick Otten 2017-07-26 16:26:23 Re: signal 11 segfaults with parallel workers
Previous Message Rick Otten 2017-07-26 15:35:47 Re: signal 11 segfaults with parallel workers