Re: Displaying and dumping of table access methods - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Displaying and dumping of table access methods
Date
Msg-id CAA4eK1LjZnHCD3Z5ej1-ex5NRrhSGNwLSnCioNk-F7yjmN+eag@mail.gmail.com
Whole thread Raw
In response to Re: Displaying and dumping of table access methods  (Andres Freund <andres@anarazel.de>)
Responses Re: Displaying and dumping of table access methods  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On Wed, Jan 9, 2019 at 10:53 PM Andres Freund <andres@anarazel.de> wrote:
>
> Hi,
>
> On 2019-01-09 18:26:16 +0530, Amit Kapila wrote:
> > On Tue, Jan 8, 2019 at 11:04 PM Andres Freund <andres@anarazel.de> wrote:
> > +1.
> >
> > >  Don't like it
> > > too much, but it seems better than the alternative. I wonder if we want
> > > one for multiple regression related issues, or whether one specifically
> > > about table AMs is more appropriate. I lean towards the latter.
> > >
> >
> > I didn't understand what is the earlier part "I wonder if we want one
> > for multiple regression related issues".  What do you mean by multiple
> > regression related issues?
>
> One flag that covers all things that make psql output less useful for
> regression test output, or one flag that just controls the table access
> method display.
>

+1 for the later (one flag that just controls the table access method
display) as that looks clean.

-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: WIP: Avoid creation of the free space map for small tables
Next
From: Donald Dong
Date:
Subject: Re: Unified logging system for command-line programs