From: Andreas Seltenreich <seltenreich@gmx.de>
To: Michael Paquier <michael.paquier@gmail.com>
Cc: PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Subject: Re: Failing assertions in indxpath.c, placeholder.c and brin_minmax.c
In-Reply-To: 
 <CAB7nPqRYCLuZsdpPKzz8trFiMj7DnKUh_XW7HR4Q+9J9JpVZpA@mail.gmail.com>
 (Michael Paquier's message of "Sun, 26 Jul 2015 22:12:21 +0900")
References: <871tfv3wor.fsf@ex.ansel.ydns.eu>
 <CAB7nPqRYCLuZsdpPKzz8trFiMj7DnKUh_XW7HR4Q+9J9JpVZpA@mail.gmail.com>
User-Agent: Gnus/5.130012 (Ma Gnus v0.12) Emacs/24.4 (gnu/linux)
Message-ID: <87twsr2gf0.fsf@ex.ansel.ydns.eu>
Date: Sun, 26 Jul 2015 15:32:19 +0200
MIME-Version: 1.0
Content-Type: text/plain
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

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


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers