Peter Geoghegan <p...@bowt.ie> writes:
> Andreas Seltenreich's sqlsmith tool has found an impressive number of
> bugs.
Indeed.
> In light of that, it seems to me that it would be reasonable for
> a contributor to write a regression test that avoids dropping database
> objects specifically so that sqlsmith had some chance of finding bugs
> after the fact, by generating a query whose plan ends up accessing
> said objects.
Traditionally, we've left around instances of various sorts of objects
so that pg_dump/pg_upgrade would be exercised on those objects. It's
possible that sqlsmith has different needs in this area, but hard to
say without more thought.
In any case, I'd say that there's never been a scorched-earth policy
so far as leaving regression test objects behind is concerned --- with
the exception of objects visible outside the regression database, ie
roles or tablespaces. I wonder whether that restriction is problematic
from this standpoint.
> For example, the new index_including.sql file drops all
> INCLUDE indexes/tables proactively, even though it looks like they're
> rather small, and in a certain sense worth keeping around.
I agree that that's a completely bad idea, especially if nothing's
been done to ensure pg_dump test coverage for the feature otherwise.
regards, tom lane
