On Wed, Sep 2, 2015 at 02:30:33PM -0300, Alvaro Herrera wrote: > > I think we should rather add *one* test that does dump/restore over the > > normal regression test database. Something similar to the pg_upgrade > > tests. And then work at adding more content to the regression test > > database - potentially sourcing from src/test/modules. > > That's another option, but we've had this idea for many years now and it > hasn't materialized. As I recall, Andrew Dunstan has a module that > tests cross-version pg_upgrade and one thing he does is dump both and > compare; the problem is that there are differences, so he keeps a count > of how many lines he expect to differ between any two releases. Or > something like that. While it's a good enough start, I don't think it's > robust enough to be in core. How would we do it?
I have shell scripts that test pg_dump restore/upgrade of every supported PG version. I also have expected pg_dump output files for every major version. This is explained in src/bin/pg_upgrade/TESTING. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
