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

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: chenjq(dot)jy(at)fujitsu(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: 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 11:06:12
Message-ID: A6A434CC-AA6D-4DD2-A26E-B6E226CCAD9B@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Julien Rouhaud also pointed out off-list that the help output and documentation
aren't in agreement about how --quiet works. In the documentation we say:

"Print fewer messages, and less detail regarding any server errors."

But the help output takes a stronger position on this:

$ ./bin/pg_amcheck --help |grep quiet
-q, --quiet don't write any messages

The latter isn't entirely true IMO, so I think we should reconcile them with
something like this while in here and fixing things anyways:

- printf(_(" -q, --quiet don't write any messages\n"));
+ printf(_(" -q, --quiet print fewer and less detailed messages\n"));

Thoughts?

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2021-08-17 11:22:33 Re: ALTER TYPE vs extension membership (was Re: BUG #17144: Upgrade from v13 to v14 with the cube extension failed)
Previous Message Heikki Linnakangas 2021-08-17 08:28:31 Re: BUG #17142: COPY ignores client_encoding for octal digit characters