Re: BUG #17148: About --no-strict-names option and --quiet option of pg_amcheck command

From: "Euler Taveira" <euler(at)eulerto(dot)com>
To: "Daniel Gustafsson" <daniel(at)yesql(dot)se>
Cc: chenjq(dot)jy(at)fujitsu(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, "Julien Rouhaud" <rjuju123(at)gmail(dot)com>
Subject: Re: BUG #17148: About --no-strict-names option and --quiet option of pg_amcheck command
Date: 2021-08-17 17:00:15
Message-ID: 429f6e0e-31eb-4741-8bf8-e9e827b3076d@www.fastmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Aug 17, 2021, at 12:57 PM, Daniel Gustafsson wrote:
> > On 17 Aug 2021, at 16:53, Euler Taveira <euler(at)eulerto(dot)com> wrote:
> > On Tue, Aug 17, 2021, at 8:06 AM, Daniel Gustafsson wrote:
>
> >> ..I think we should reconcile them with
> >> something like this while in here and fixing things anyways:
>
> > I suggest that it should be a message that we already use in another binaries
> > such as "do not print any output, except for errors".
>
> Well, problem is that it’s plain not true. If you pass --quiet --verbose you
> will get a lot of output, albeit less than if not using --quiet. Consistency
> with other tools is obviously good, but only when it’s correct IMO.
Indeed, it is not a good design. It should be one option --verbose that
increases the verbosity according to a number or an enum value. --verbose=0
means "quiet". However, that ship has sailed.

--
Euler Taveira
EDB https://www.enterprisedb.com/

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2021-08-17 18:27:10 Re: BUG #17150: Unexpected outputs from the query
Previous Message PG Bug reporting form 2021-08-17 16:30:10 BUG #17150: Unexpected outputs from the query