Remove --quiet option from pg_amcheck
Daniel Gustafsson <dgustafsson@postgresql.org>
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 <chenjq.jy@fujitsu.com> Reviewed-by: Julien Rouhaud <rjuju123@gmail.com> Discussion: https://postgr.es/m/17148-b5087318e2b04fc6@postgresql.org Backpatch-through: 14
Files
| Path | Change | +/− |
|---|---|---|
| doc/src/sgml/ref/pg_amcheck.sgml | modified | +0 −12 |
| src/bin/pg_amcheck/pg_amcheck.c | modified | +13 −25 |
| src/bin/pg_amcheck/t/002_nonesuch.pl | modified | +5 −1 |
| src/bin/pg_amcheck/t/003_check.pl | modified | +1 −1 |
| src/bin/pg_amcheck/t/005_opclass_damage.pl | modified | +1 −1 |
Documentation touched
Discussion
- BUG #17148: About --no-strict-names option and --quiet option of pg_amcheck command 16 messages · 2021-08-17 → 2021-08-27