| From: | Rick Otten <rottenwindfish(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(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 15:35:47 |
| Message-ID: | CAMAYy4KBharY03QrodHPc33A7yo19g+QAN-2LXJqDNKWGd-aUw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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 I could get it to fail every time I ran the query, I'm sure I could
build a test case for you. Sorry. :-(
On Wed, Jul 26, 2017 at 10:58 AM, Michael Paquier <michael(dot)paquier(at)gmail(dot)com
> wrote:
> 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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-07-26 15:43:22 | Re: signal 11 segfaults with parallel workers |
| Previous Message | Michael Paquier | 2017-07-26 14:58:56 | Re: signal 11 segfaults with parallel workers |