Andreas Seltenreich <seltenre...@gmx.de> writes:
> sqlsmith triggered the following assertion in master (c188204).
> TRAP: FailedAssertion("!(!bms_overlap(joinrelids, sjinfo->min_lefthand))",
> File: "joinrels.c", Line: 500)
Cool, I'll take a look.
> As usual, the query is against the regression database. It is rather
> unwieldy⦠I wonder if I should stop working on new grammar rules and
> instead work on some post-processing that prunes the AST as much as
> possible while maintaining the failure mode.
Probably not really worth the trouble; I find it's usually easy to
produce a minimized test case after the failure cause is understood.
What concerns me more is that what you're finding is only cases that trip
an assertion sanity check. It seems likely that you're also managing to
trigger other bugs with less drastic consequences, such as "could not
devise a query plan" failures or just plain wrong answers. I'm not sure
how we could identify wrong answers automatically :-( but it might be
worth checking for XX000 SQLSTATE responses, since generally that should
be a can't-happen case. (Or if it can happen, we need to change the
errcode.)
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
