On Thu, Apr 6, 2017 at 7:48 AM, Michael Paquier <michael.paqu...@gmail.com> wrote: > On Wed, Apr 5, 2017 at 10:24 PM, Stephen Frost <sfr...@snowman.net> wrote: >> * Michael Paquier (michael.paqu...@gmail.com) wrote: >>> 1) Initialize the old cluster and start it. >>> 2) create a bunch of databases with full range of ascii characters. >>> 3) Run regression tests. >>> 4) Take dump on old cluster. >>> 4) Stop the old cluster. >>> 5) Initialize the new cluster. >>> 6) Run pg_upgrade. >>> 7) Start new cluster. >>> 8) Take dump from it. >>> 9) Run deletion script (Oops forgot this part!) >> >> Presumably the check to match the old dump against the new one is also >> performed? > > Yes. That's run with command_ok() at the end.
Attached is an updated patch to use --no-sync with pg_dumpall calls. -- Michael
pgupgrade-tap-test-v3.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
