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 CAA4eK1KyzMn1YwvbD-4XAZg9oZFRZ8Es0t9zp4DX2mhVMzEYZA@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  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Tue, Jan 8, 2019 at 11:04 PM Andres Freund <andres@anarazel.de> wrote:
>
> Hi,
>
> On 2019-01-08 11:30:56 +0100, Peter Eisentraut wrote:
> > On 08/01/2019 00:56, Andres Freund wrote:
> > > A patch at [2] adds display of a table's access method to \d+ - but that
> > > means that running the tests with a different default table access
> > > method (e.g. using PGOPTIONS='-c default_table_access_method=...)
> > > there'll be a significant number of test failures, even though the test
> > > results did not meaningfully differ.
> >
> > For psql, a variable that hides the access method if it's the default.
>
> Yea, I think that seems the least contentious solution.
>

+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?

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


pgsql-hackers by date:

Previous
From: Mithun Cy
Date:
Subject: Re: WIP: Avoid creation of the free space map for small tables
Next
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] pgbench - allow to store select results into variables