From: | Andreas Seltenreich <seltenreich(at)gmx(dot)de> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Failing assertions in indxpath.c, placeholder.c and brin_minmax.c |
Date: | 2015-07-26 13:32:19 |
Message-ID: | 87twsr2gf0.fsf@ex.ansel.ydns.eu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
> database to retrieve the schema, what is it exactly in the case of
> those failures?
I used the database "regression" that pg_regress leaves behind when you
remove the --temp-install from it's default invocation through make
check. Sorry about not being explicit about that.
So, dropping one of the queries into src/test/regress/sql/smith.sql and
invoking
make check EXTRA_TESTS=smith
was all that was needed to integrate them. I was then able to perform
"git bisect run" on this command. Er, plus consing the expected output
file.
I'm using the regression db a lot when hacking on sqlsmith, as it
contains much more nasty things than your average database.
regards
andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-07-26 14:07:12 | Re: Failing assertions in indxpath.c, placeholder.c and brin_minmax.c |
Previous Message | Michael Paquier | 2015-07-26 13:12:21 | Re: Failing assertions in indxpath.c, placeholder.c and brin_minmax.c |