On Wed, May 11, 2016 at 09:40:09AM -0400, Peter Eisentraut wrote: > Not that that would be useless, but note that the value in this case (and > most others) comes from having a candidate object in the database before > upgrade that exercises the particular problem, mostly independent of what > version you upgrade from and to. So far the way to do that is to leave > "junk" in the regression test database, but that's clearly a bit silly. > > I think the way forward is to create a TAP test suite for pg_upgrade that > specifically exercises a lot of scenarios with small purpose-built test > databases. > > Then, the problem of having to compare dump output across versions also goes > away more easily.
I do have some small tests like for tablespaces. I am attaching the SQL script, if that is helpful. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +
-- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers