| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Andreas Seltenreich <seltenreich(at)gmx(dot)de> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [sqlsmith] Parallel worker executor crash on master |
| Date: | 2017-12-16 07:23:06 |
| Message-ID: | CAA4eK1+C5wXvK+yaG65+p1O5Ud4qYMbQDEUP2bqzh0mTPe27LQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Dec 16, 2017 at 12:57 AM, Andreas Seltenreich
<seltenreich(at)gmx(dot)de> wrote:
> Hi,
>
> sqlsmith just crashed a parallel worker while testing master at
> 699bf7d05c. I can reproduce it with the following recipe on a fresh
> regression database. Backtrace and query plan below as well.
>
This seems to be another symptom of the problem related to
es_query_dsa for which Thomas has sent a patch on a different thread
[1]. After applying that patch, I am not able to see the problem. I
think due to the wrong usage of dsa across nodes, it can lead to
sending some wrong values for params to workers.
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Seltenreich | 2017-12-16 09:13:32 | Re: [sqlsmith] Parallel worker executor crash on master |
| Previous Message | David Rowley | 2017-12-16 06:05:57 | Re: [HACKERS] Runtime Partition Pruning |