On Sun, Jul 26, 2015 at 11:15 PM, Peter Geoghegan wrote:
> The SQLite people have been using a tool like this for some time.
> They've also had luck finding bugs with a generic fuzz-testing tool
> called "american fuzzy lop" (yes, seriously, that's what it's called),
> which apparently is the stat
Tom Lane wrote:
> Alvaro Herrera writes:
> > Tom Lane wrote:
> >> Bottom line is that somebody failed to consider the possibility of a
> >> null comparison value reaching the BRIN index lookup machinery.
> >> The code stanza that's failing supposes that only IS NULL or IS NOT NULL
> >> tests could
Alvaro Herrera writes:
> Tom Lane wrote:
>> Bottom line is that somebody failed to consider the possibility of a
>> null comparison value reaching the BRIN index lookup machinery.
>> The code stanza that's failing supposes that only IS NULL or IS NOT NULL
>> tests could have SK_ISNULL set, but tha
Tom Lane wrote:
> Bottom line is that somebody failed to consider the possibility of a
> null comparison value reaching the BRIN index lookup machinery.
> The code stanza that's failing supposes that only IS NULL or IS NOT NULL
> tests could have SK_ISNULL set, but that's just wrong.
I think the
Andreas Seltenreich writes:
> I let sqlsmith run during the night, and it did no longer trigger the
> first two. During roughly a million random queries it triggered the
> already mentioned brin one 10 times, but there was also one instance of
> this new one in the log:
> TRAP: FailedAssertion("
Andreas Seltenreich writes:
> Tom Lane writes:
>> I've fixed the first two of these --- thanks for the report!
> I let sqlsmith run during the night, and it did no longer trigger the
> first two. During roughly a million random queries it triggered the
> already mentioned brin one 10 times, but
Tom Lane wrote:
> Bottom line is that somebody failed to consider the possibility of a
> null comparison value reaching the BRIN index lookup machinery.
> The code stanza that's failing supposes that only IS NULL or IS NOT NULL
> tests could have SK_ISNULL set, but that's just wrong.
Hm, okay, wi
Tom Lane writes:
> Andreas Seltenreich writes:
>> when running my random query generator contraption[1] against the
>> regression database of 9.5 or master, it occasionally triggers one of
>> the following three assertions.
>
> I've fixed the first two of these --- thanks for the report!
I let s
On Sun, Jul 26, 2015 at 10:32 PM, Andreas Seltenreich
wrote:
> Michael Paquier writes:
>
> >> Footnotes:
> >> [1] https://github.com/anse1/sqlsmith
> >
> > This is really interesting stuff. I think that it would be possible to
> > extract self-contained test cases from your tool and those querie
On Sun, Jul 26, 2015 at 7:07 AM, Tom Lane wrote:
> Andreas Seltenreich writes:
>> when running my random query generator contraption[1] against the
>> regression database of 9.5 or master, it occasionally triggers one of
>> the following three assertions.
>
> Very very cool tool! Please keep doi
Andreas Seltenreich writes:
> when running my random query generator contraption[1] against the
> regression database of 9.5 or master, it occasionally triggers one of
> the following three assertions.
I've fixed the first two of these --- thanks for the report!
> ,[ git bisect ]
> | first
Andreas Seltenreich writes:
> when running my random query generator contraption[1] against the
> regression database of 9.5 or master, it occasionally triggers one of
> the following three assertions.
Very very cool tool! Please keep doing that testing.
The first two seem to be planner problem
Michael Paquier writes:
>> Footnotes:
>> [1] https://github.com/anse1/sqlsmith
>
> This is really interesting stuff. I think that it would be possible to
> extract self-contained test cases from your tool and those queries to
> reproduce the failures. It is written that this tools connects to a
>
On Sun, Jul 26, 2015 at 9:55 PM, Andreas Seltenreich wrote:
> when running my random query generator contraption[1] against the
> regression database of 9.5 or master, it occasionally triggers one of
> the following three assertions. Someone more knowledgeable might want
> to take a look at them.
Hi,
when running my random query generator contraption[1] against the
regression database of 9.5 or master, it occasionally triggers one of
the following three assertions. Someone more knowledgeable might want
to take a look at them...
-- FailedAssertion("!(outer_rel->rows > 0)", File: "indxpath
15 matches
Mail list logo
