Re: [sqlsmith] Parallel worker crash on seqscan - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [sqlsmith] Parallel worker crash on seqscan
Date
Msg-id CA+TgmoYfDAgdt1EyJm+DEiCkizAo9fYhQNFPmdVrbmqm6vyneQ@mail.gmail.com
Whole thread Raw
In response to Re: [sqlsmith] Parallel worker crash on seqscan  (Andreas Seltenreich <seltenreich@gmx.de>)
Responses Re: [sqlsmith] Parallel worker crash on seqscan
List pgsql-hackers
On Mon, Nov 21, 2016 at 5:14 PM, Andreas Seltenreich <seltenreich@gmx.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



pgsql-hackers by date:

Previous
From: Andreas Seltenreich
Date:
Subject: Re: [sqlsmith] Parallel worker crash on seqscan
Next
From: Tom Lane
Date:
Subject: Re: [sqlsmith] Parallel worker crash on seqscan