| From: | Rick Otten <rottenwindfish(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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 16:26:23 |
| Message-ID: | CAMAYy4K66ZXoOKKHXb3Tm8RL-PYydg_YfZzFJxFDE8U+fn-yNw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
I'll restart the database tonight to pick up the ulimit change and let you
know if I capture a core file in the near future.
On Wed, Jul 26, 2017 at 11:43 AM, 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.
>
> regards, tom lane
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Gould | 2017-07-26 20:38:34 | Re: signal 11 segfaults with parallel workers |
| Previous Message | Tom Lane | 2017-07-26 15:43:22 | Re: signal 11 segfaults with parallel workers |