Postgres Pro
Downloads
Home   >   mailing lists

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

From Michael Paquier
Subject Re: [HACKERS] Rewriting the test of pg_upgrade as a TAP test
Date
Msg-id CAB7nPqRZXui-Z6zaFiSc0HxSwev7Rhi=P4R-_qm_0fUvNy+emQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Rewriting the test of pg_upgrade as a TAP test  (Stephen Frost <sfrost@snowman.net>)
Responses Re: [HACKERS] Rewriting the test of pg_upgrade as a TAP test  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
Tree view 
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.
-- 
Michael

pgsql-hackers by date:

Previous
From: Petr Jelinek
Date:
Subject: Re: [HACKERS] Logical replication launcher useswal_retrieve_retry_interval
Next
From: Stephen Frost
Date:
Subject: Re: [HACKERS] Rewriting the test of pg_upgrade as a TAP test