Re: pgsql: Make VACUUM accept 1 and 0 as a boolean value.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Fujii Masao <fujii(at)postgresql(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Make VACUUM accept 1 and 0 as a boolean value.
Date: 2019-05-20 18:09:40
Message-ID: 24497.1558375780@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2019-05-20 13:46:55 -0400, Tom Lane wrote:
>> If there were a way to get prove to be absolutely quiet (its --quiet is
>> a joke unfortunately), I'd lobby for a switch to make pg_regress quiet
>> too. The amount of useless noise this recipe generates is annoying,
>> and tends to make it hard to find where the actual error is when
>> there is one.

> Indeed. Couldn't we just invent that on our end? I.e. in our prove
> invocation, just redirect the output?

What I'd like, for both prove and pg_regress, is to print something
about failing tests and otherwise be quiet. Simple redirection won't
do that. Plus it'd be hard to fit that in with the case where you
don't want it to be quiet.

> The most annoying noise imo is the pg_upgrade test. The set -x and the
> fact that it resets MAKEFLAGS makes that pretty annoying.

Agreed, that could be improved independently of other things.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2019-05-20 20:35:05 Re: pgsql: Make VACUUM accept 1 and 0 as a boolean value.
Previous Message Andres Freund 2019-05-20 18:00:27 Re: pgsql: Make VACUUM accept 1 and 0 as a boolean value.