Re: [COMMITTERS] pgsql: Sync pg_dump and pg_dumpall output

From: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Subject: Re: [COMMITTERS] pgsql: Sync pg_dump and pg_dumpall output
Date: 2017-03-22 15:59:32
Message-ID: 75e1b6ff-c3d5-9a26-e38b-3cb22a099ff0@2ndQuadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 03/22/2017 11:39 AM, Stephen Frost wrote:
> Andrew,
>
> * Andrew Dunstan (andrew(at)dunslane(dot)net) wrote:
>> Sync pg_dump and pg_dumpall output
> This probably should have adjusted all callers of pg_dump in the
> regression tests to use the --no-sync option, otherwise we'll end up
> spending possibly a good bit of time calling fsync() during the
> regression tests unnecessairly.
>

All of them? The imnpact is not likely to be huge in most cases
(possibly different on Windows). On crake, the bin-check stage actually
took less time after the change than before, so I suspect that the
impact will be pretty small.

Still I agree that we should have tests for both cases.

Michael, do you want to look at that? If not, I'll take a look but it
will probably be next week before I get to it.

cheers

andrew

--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Stephen Frost 2017-03-22 16:10:07 Re: [COMMITTERS] pgsql: Sync pg_dump and pg_dumpall output
Previous Message Stephen Frost 2017-03-22 15:39:20 Re: [COMMITTERS] pgsql: Sync pg_dump and pg_dumpall output

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2017-03-22 15:59:42 Re: Logical decoding on standby
Previous Message Erik Rijkers 2017-03-22 15:51:06 bug/oversight in TestLib.pm and PostgresNode.pm