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

From Tom Lane
Subject Re: BUG #17148: About --no-strict-names option and --quiet option of pg_amcheck command
Date
Msg-id 1426271.1629294170@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #17148: About --no-strict-names option and --quiet option of pg_amcheck command  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: BUG #17148: About --no-strict-names option and --quiet option of pg_amcheck command  (Magnus Hagander <magnus@hagander.net>)
List pgsql-bugs
Daniel Gustafsson <daniel@yesql.se> writes:
>> On 18 Aug 2021, at 13:44, Peter Eisentraut <peter.eisentraut@enterprisedb.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?

It's going to become much harder to change pg_amcheck's user-visible
behavior once it's shipped in a release.  Better to fix it now while
there are not backwards-compatibility concerns.

            regards, tom lane



pgsql-bugs by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: BUG #17148: About --no-strict-names option and --quiet option of pg_amcheck command
Next
From: Magnus Hagander
Date:
Subject: Re: BUG #17148: About --no-strict-names option and --quiet option of pg_amcheck command