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

From Magnus Hagander
Subject Re: BUG #17148: About --no-strict-names option and --quiet option of pg_amcheck command
Date
Msg-id CABUevExiPH790T7+xmFRHW1cht4d8VH88LZ9EP1FrKj25ydy1Q@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17148: About --no-strict-names option and --quiet option of pg_amcheck command  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #17148: About --no-strict-names option and --quiet option of pg_amcheck command  (Daniel Gustafsson <daniel@yesql.se>)
List pgsql-bugs
On Wed, Aug 18, 2021 at 3:43 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> 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.

+<several>. Let's just get it done now. I doubt many people have had
the time to integrate it into their scripts and such yet, and since
it's a beta...

-- 
 Magnus Hagander
 Me: https://www.hagander.net/
 Work: https://www.redpill-linpro.com/



pgsql-bugs by date:

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