Re: Include access method in listTables output - Mailing list pgsql-hackers

From vignesh C
Subject Re: Include access method in listTables output
Date
Msg-id CALDaNm0-VaXY_w38E1FAFa-xmKOqOOikhge-Vwpe1+uYwCVhSw@mail.gmail.com
Whole thread Raw
In response to Re: Include access method in listTables output  (Georgios <gkokolatos@protonmail.com>)
Responses Re: Include access method in listTables output  (Georgios <gkokolatos@protonmail.com>)
List pgsql-hackers
On Tue, Jun 16, 2020 at 6:13 PM Georgios <gkokolatos@protonmail.com> wrote:
> > Few comments:
> >
> > -   if (pset.sversion >= 120000)
> >
> > -   appendPQExpBufferStr(&buf,
> >
> > -   "\n LEFT JOIN pg_catalog.pg_am am ON am.oid = c.relam");
> >
> >     Should we include pset.hide_tableam check along with the version check?
>
> I opted against it, since it seems more intuitive to have a single
> switch and placed on the display part. A similar pattern can be found
> in describeOneTableDetails(). I do not hold a strong opinion and will
> gladly ament if insisted upon.
>

I felt we could add that check as we might be including
pg_catalog.pg_am in cases even though we really don't need it.

Regards,
Vignesh
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Erik Rijkers
Date:
Subject: git.postgresql.org ok?
Next
From: Ranier Vilela
Date:
Subject: Possible NULL pointer deferenced (src/interfaces/libpq/fe-exec.c(line 563)