Re: Include access method in listTables output

From: vignesh C <vignesh21(at)gmail(dot)com>
To: Georgios <gkokolatos(at)protonmail(dot)com>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Include access method in listTables output
Date: 2020-06-15 01:20:10
Message-ID: CALDaNm0EJRpKUeKAv0qhH_CtG31iLExHGkxZGRxfB2o-P9Y0Lw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 9, 2020 at 6:45 PM Georgios <gkokolatos(at)protonmail(dot)com> wrote:
>

> > Please add it to the commitfest at https://commitfest.postgresql.org/28/
>
> Thank you very much for your time. Added to the commitfest as suggested.

Patch applies cleanly, make check & make check-world passes.

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?

+ if (pset.sversion >= 120000 && !pset.hide_tableam)
+ {
+ appendPQExpBuffer(&buf,
+ ",\n am.amname as \"%s\"",
+ gettext_noop("Access Method"));
+ }

Braces can be removed & the second line can be combined with earlier.

We could include the test in psql file by configuring HIDE_TABLEAM.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2020-06-15 01:55:27 Re: valgrind versus pg_atomic_init()
Previous Message Michael Paquier 2020-06-15 00:18:28 Re: [PATCH] Initial progress reporting for COPY command