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

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Cc: Euler Taveira <euler(at)eulerto(dot)com>, chenjq(dot)jy(at)fujitsu(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, 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-18 12:35:06
Message-ID: 53F68B28-4FDB-4AC9-882C-A620D3389EB0@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On 18 Aug 2021, at 13:44, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:

> I think this both of these things could be deleted and we could get rid of the --quiet option, to simplify all this.

It simplifies the pg_amcheck code a bit, but it at the same time complicates
the tests as they are currently written. Not sure that we want to change that
much as this point in the 14 cycle?

> Neither of these behaviors is in common with any other PostgreSQL tool.

That I agree with.

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2021-08-18 13:42:50 Re: BUG #17148: About --no-strict-names option and --quiet option of pg_amcheck command
Previous Message Masahiko Sawada 2021-08-18 11:52:51 Re: BUG #17151: A SEGV in optimizer