Re: Segfault 11 on PG10 with max_parallel_workers_per_gather>3

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stefan Tzeggai <tzeggai(at)empirica-systeme(dot)de>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Segfault 11 on PG10 with max_parallel_workers_per_gather>3
Date: 2017-10-25 14:34:35
Message-ID: 15437.1508942075@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Stefan Tzeggai <tzeggai(at)empirica-systeme(dot)de> writes:
> I can reproduce a segfault by executing a query.

That sounds like a bug, all right, but you've not provided enough
detail for anyone else to reproduce it. A self-contained test
case would be the best thing.

If you can't provide that, it's possible that a stack trace from
the core dump would be enough info to diagnose the problem, but
no promises ...

https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2017-10-25 15:32:52 Re: BUG #14849: jsonb_build_object doesn't like VARIADIC calls very much
Previous Message Stefan Tzeggai 2017-10-25 12:16:39 Segfault 11 on PG10 with max_parallel_workers_per_gather>3