Re: signal 11 segfaults with parallel workers

From: David Gould <daveg(at)sonic(dot)net>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: signal 11 segfaults with parallel workers
Date: 2017-07-26 20:38:34
Message-ID: 20170726133834.05362c34@engels
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, 26 Jul 2017 11:43:22 -0400
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> 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.

If you are using pg_ctl to start postgresql you can add the "-c" flag to your
pg_ctl command to enable core files.

-dg

--
David Gould 510 282 0869 daveg(at)sonic(dot)net
If simplicity worked, the world would be overrun with insects.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message raviraj.suddhala 2017-07-27 04:35:47 BUG #14762: error while running report
Previous Message Rick Otten 2017-07-26 16:26:23 Re: signal 11 segfaults with parallel workers