database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-30 11:03:19 +03:00
Code Activity

Remove --quiet option from pg_amcheck

Browse Source 
Using --quiet in combination with --no-strict-names didn't work as
documented, a warning message was still emitted. Since the --quiet
flag was working in an unconventional way to other utilities, fix
by removing the functionality instead.

Backpatch through 14 where pg_amcheck was introduced.

Bug: 17148
Reported-by: Chen Jiaoqian <chenjq.jy@fujitsu.com>
Reviewed-by: Julien Rouhaud <rjuju123@gmail.com>
Discussion: https://postgr.es/m/17148-b5087318e2b04fc6@postgresql.org
Backpatch-through: 14
This commit is contained in:
Daniel Gustafsson
2021-08-20 12:44:54 +02:00
parent 5b3f471ff2
commit 9a9c8b9201
5 changed files with 20 additions and 40 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
doc/src/sgml/ref/pg_amcheck.sgml
View File

@ -289,8 +289,6 @@ PostgreSQL documentation
<literal>--table</literal>, <literal>--index</literal>,
or <literal>--relation</literal> matches no objects, it is a fatal
error. This option downgrades that error to a warning.
If this option is used with <literal>--quiet</literal>, the warning
will be suppressed as well.
</para>
</listitem>
</varlistentry>
@ -553,16 +551,6 @@ PostgreSQL documentation
</listitem>
</varlistentry>
<varlistentry>
<term><option>-q</option></term>
<term><option>--quiet</option></term>
<listitem>
<para>
Print fewer messages, and less detail regarding any server errors.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-P</option></term>
<term><option>--progress</option></term>