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
