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

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Euler Taveira <euler(at)eulerto(dot)com>
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 15:57:36
Message-ID: F5A1A42D-184C-46B7-8FBF-17AA000D28E0@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> 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.

--
Daniel Gustafsson https://vmware.com/

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2021-08-17 16:30:10 BUG #17150: Unexpected outputs from the query
Previous Message Euler Taveira 2021-08-17 14:53:07 Re: BUG #17148: About --no-strict-names option and --quiet option of pg_amcheck command