From 92ce7f527960ca672d2ad70e61442f4e5b3bb641 Mon Sep 17 00:00:00 2001 From: Daniel Gustafsson Date: Fri, 20 Aug 2021 12:44:54 +0200 Subject: Remove --quiet option from pg_amcheck 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 Reviewed-by: Julien Rouhaud Discussion: https://postgr.es/m/17148-b5087318e2b04fc6@postgresql.org Backpatch-through: 14 --- doc/src/sgml/ref/pg_amcheck.sgml | 12 ------------ 1 file changed, 12 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/ref/pg_amcheck.sgml b/doc/src/sgml/ref/pg_amcheck.sgml index 46d12110b19..d00c48d0e79 100644 --- a/doc/src/sgml/ref/pg_amcheck.sgml +++ b/doc/src/sgml/ref/pg_amcheck.sgml @@ -289,8 +289,6 @@ PostgreSQL documentation --table, --index, or --relation matches no objects, it is a fatal error. This option downgrades that error to a warning. - If this option is used with --quiet, the warning - will be suppressed as well. @@ -553,16 +551,6 @@ PostgreSQL documentation - - - - - - Print fewer messages, and less detail regarding any server errors. - - - - -- cgit v1.2.3