On Sun, Dec 17, 2017 at 12:26 PM, Andreas Seltenreich
wrote:
> Thomas Munro writes:
>
>> On Sat, Dec 16, 2017 at 10:13 PM, Andreas Seltenreich
>> wrote:
>>> Core was generated by `postgres: smith regression [local] SELECT
>>> '.
>>> Program terminated with signal SIGSEGV,
Thomas Munro writes:
> On Sat, Dec 16, 2017 at 10:13 PM, Andreas Seltenreich
> wrote:
>> Core was generated by `postgres: smith regression [local] SELECT
>>'.
>> Program terminated with signal SIGSEGV, Segmentation fault.
>> #0 gather_getnext (gatherstate=0x555a5fff1350)
On Sat, Dec 16, 2017 at 10:13 PM, Andreas Seltenreich
wrote:
> Amit Kapila writes:
>
>> 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
>> thi
Amit Kapila writes:
> 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
> sendi
On Sat, Dec 16, 2017 at 12:57 AM, Andreas Seltenreich
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
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.
regards,
Andreas
--8<---cut here---start->8---
set min_parall
