Re: [PATCH] Reduce src/test/recovery verbosity - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: [PATCH] Reduce src/test/recovery verbosity
Date
Msg-id 20170330125236.GT9812@tamriel.snowman.net
Whole thread Raw
In response to Re: [PATCH] Reduce src/test/recovery verbosity  (Stephen Frost <sfrost@snowman.net>)
Responses Re: [PATCH] Reduce src/test/recovery verbosity  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [PATCH] Reduce src/test/recovery verbosity  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: [PATCH] Reduce src/test/recovery verbosity  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
Michael,

* Michael Paquier (michael.paquier@gmail.com) wrote:
> On Thu, Mar 30, 2017 at 4:08 AM, Stephen Frost <sfrost@snowman.net> wrote:
> >> > If there's a way to change the verbosity for just those scripts, I'd be
> >> > happy to do that, if we're unable to agree on reducing it across the
> >> > board..
> >>
> >> I'd rather silence only scripts that are overly verbose.
> >
> > I'm fine with that, but how?
>
> The important point to me is not to show the tests that passed, it is
> to show the tests that are failing when running them. So I would
> suggest to just remove the --verbose flag in PROVE_FLAGS. If you do
> so, the test of pg_dump would show up like that, printing as well a
> count number while running:

Right, but you can't do that for just pg_dump.

I'd be fine with removing --verbose globally, as your patch does, but
there was some argument that we then would have long 'quiet' periods.
I haven't had a chance to go test if that's really the case yet though.

Thanks!

Stephen

pgsql-hackers by date:

Previous
From: Pavan Deolasee
Date:
Subject: Re: Patch: Write Amplification Reduction Method (WARM)
Next
From: Michael Paquier
Date:
Subject: Re: [PATCH] Reduce src/test/recovery verbosity