| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Stefan Tzeggai <tzeggai(at)empirica-systeme(dot)de> |
| Cc: | PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: PG10 Segfault 11 on default Ubuntu 16.04 installs |
| Date: | 2017-11-08 12:59:45 |
| Message-ID: | CAA4eK1LCWYV7GdscGKnx6wRjOTr70R-vRae4zTbHvPyLHQUUdw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, Nov 8, 2017 at 5:20 PM, Stefan Tzeggai
<tzeggai(at)empirica-systeme(dot)de> wrote:
> Hi
>
> The segfaults thrown when I run my application on PG10 got worse. I have
> found more segfaults even when max_parallel_workers_per_gather is left
> default.
>
> I have been able to create a 6Mb PG10 dump that I can be imported into a
> vigin PG10 install on Ubuntu 16.04 and I have a query that segfaults
> PG10 100% (on my mashines at least).
>
> The dataset has been wiped of sensitive data, but it still should not go
> public. I will send a password by email to all PG-hackers interested.
>
Can you share the password with me? My guess is that this is related
to Parallel Bitmap Heap Scan as that is a newly introduced feature in
PG10 and the previous email shows that in the plan.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dilip Kumar | 2017-11-08 13:24:00 | Re: Segfault 11 on PG10 with max_parallel_workers_per_gather>3 |
| Previous Message | Stefan Tzeggai | 2017-11-08 11:50:20 | Re: PG10 Segfault 11 on default Ubuntu 16.04 installs |