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] Failed assertion in BecomeLockGroupLeader |
Date: | 2016-04-29 07:40:24 |
Message-ID: | CAA4eK1JfhAKcrxfq2qbff=veZt88Vc425Dw+BztCS8aZ9cqjtA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Apr 29, 2016 at 12:01 PM, Andreas Seltenreich <seltenreich(at)gmx(dot)de>
wrote:
>
> Hi,
>
> tonight's sqlsmith run yielded another core dump:
>
> TRAP: FailedAssertion("!(MyProc->lockGroupLeader == ((void *)0))", File:
"proc.c", Line: 1787)
>
> I couldn't identifiy a query for it though: debug_query_string is empty.
> Additionally, the offending query was not reported in the error context
> as it typically is for non-parallel executor crashes.
>
From callstack below, it is clear that the reason for core dump is that
Gather node is pushed below another Gather node which makes worker execute
the Gather node. Currently there is no support in workers to launch
another workers and ideally such a plan should not be generated. It will
be helpful if you can find the offending query or plan corresponding to it?
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2016-04-29 07:40:57 | Re: Timeline following for logical slots |
Previous Message | Fabien COELHO | 2016-04-29 07:22:18 | Re: [BUGS] Breakage with VACUUM ANALYSE + partitions |