Re: [sqlsmith] Failed assertion in BecomeLockGroupLeader
| От | Simon Riggs |
|---|---|
| Тема | Re: [sqlsmith] Failed assertion in BecomeLockGroupLeader |
| Дата | |
| Msg-id | CANP8+j+O7cfZdYAmZ=8D7a_j8ejZrEG0NZAj5sHj-2JRK-v+Gw@mail.gmail.com обсуждение исходный текст |
| Ответ на | [sqlsmith] Failed assertion in BecomeLockGroupLeader (Andreas Seltenreich <seltenreich@gmx.de>) |
| Ответы |
Re: [sqlsmith] Failed assertion in BecomeLockGroupLeader
|
| Список | pgsql-hackers |
On 29 April 2016 at 08:31, Andreas Seltenreich <seltenreich@gmx.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.
It's good that the input is fuzzed, but there needs to be a way to re-run identical fuzzing or a way to backtrack to find what broke. Not much point finding bugs we can't identify later.
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: