Re: [HACKERS] Rewriting the test of pg_upgrade as a TAP test - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: [HACKERS] Rewriting the test of pg_upgrade as a TAP test
Date
Msg-id 20170414122418.GC9812@tamriel.snowman.net
Whole thread Raw
In response to Re: [HACKERS] Rewriting the test of pg_upgrade as a TAP test  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
* Michael Paquier (michael.paquier@gmail.com) wrote:
> On Fri, Apr 14, 2017 at 8:03 PM, Stephen Frost <sfrost@snowman.net> wrote:
> > Some of those were specifically left around to test those code paths.
> > I'm not sure if these were those or not though, Andrew was the one who
> > reviewed the various pg_dumpall calls to add --no-sync in places.
>
> Well, Andrew has pushed the patch I have written, and the calls of
> pg_dumpall in pg_upgrade use --no-sync. The ones intentionally left
> are in src/bin/pg_dump/t/002_pg_dump.pl.

Ok. :)

Thanks!

Stephen

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] Rewriting the test of pg_upgrade as a TAP test
Next
From: Michael Paquier
Date:
Subject: Re: [HACKERS] Letting the client choose the protocol to use during aSASL exchange