| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andreas Seltenreich <seltenreich(at)gmx(dot)de> |
| Cc: | Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: [sqlsmith] Parallel worker crash on seqscan |
| Date: | 2016-11-21 22:16:23 |
| Message-ID: | CA+TgmoYfDAgdt1EyJm+DEiCkizAo9fYhQNFPmdVrbmqm6vyneQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Nov 21, 2016 at 5:14 PM, Andreas Seltenreich <seltenreich(at)gmx(dot)de> wrote:
> Ashutosh Sharma writes:
>>> the following query appears to reliably crash parallel workers on master
>>> as of 0832f2d.
>
>> As suggested, I have tried to reproduce this issue on *0832f2d* commit but
>> could not reproduce it.
>
> as Tom pointed out earlier, I had secretly set parallel_setup_cost and
> parallel_tuple_cost to 0. I assumed these were irrelevant when
> force_parallel_mode is on. I'll do less assuming and more testing on a
> vanilla install on future reports.
>
> Sorry for the inconvenience,
Don't sweat it! Your sqlsmith fuzz testing has been extremely valuable.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-11-21 22:30:09 | Re: [sqlsmith] Parallel worker crash on seqscan |
| Previous Message | Andreas Seltenreich | 2016-11-21 22:14:20 | Re: [sqlsmith] Parallel worker crash on seqscan |