Re: signal 11 segfaults with parallel workers

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Rick Otten <rottenwindfish(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: signal 11 segfaults with parallel workers
Date: 2017-07-26 14:58:56
Message-ID: CAB7nPqR4d3uvRZWHN94M13CiqnvBBywug9AZsMmi8P4TCqA8MQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Jul 26, 2017 at 4:47 PM, Rick Otten <rottenwindfish(at)gmail(dot)com> wrote:
> If you need anything else, please let me know. I wish I could reproduce the
> error every time I ran the query, but it doesn't seem to work that way, and
> of course now the query plan is completely different, but I'm sure I can run
> other queries that would induce parallel sequence scans on my tables.

Backtrace of the core files generated with debug symbols on, and a
minimum test case to reproduce the failure usually help.
--
Michael

In response to

Responses

Browse pgsql-bugs by date

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