Re: BUG #17148: About --no-strict-names option and --quiet option of pg_amcheck command
Euler Taveira <euler@eulerto.com>
From: "Euler Taveira" <euler@eulerto.com>
To: "Daniel Gustafsson" <daniel@yesql.se>
Cc: chenjq.jy@fujitsu.com, pgsql-bugs@lists.postgresql.org,
"Julien Rouhaud" <rjuju123@gmail.com>
Date: 2021-08-17T17:00:15Z
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@eulerto.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/
Commits
-
Remove --quiet option from pg_amcheck
- 9a9c8b92018d 15.0 landed
- 92ce7f527960 14.0 landed