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-07-05 01:43:10 |
Message-ID: | CALDaNm23zSPK6x1ybPkCkGJMixqm0i=9=DUwPfWEyaHVL=T7CA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jun 30, 2020 at 2:53 PM Georgios <gkokolatos(at)protonmail(dot)com> wrote:
>
>
> As promised, I gladly ament upon your request. Also included a fix for
> a minor oversight in tests, they should now be stable. Finally in this
> version, I extended a bit the logic to only include the access method column
> if the relations displayed can have one, for example sequences.
>
Patch applies cleanly, make check & make check-world passes.
One comment:
+ if (pset.sversion >= 120000 && !pset.hide_tableam &&
+ (showTables || showViews || showMatViews ||
showIndexes))
+ appendPQExpBuffer(&buf,
+ ",\n
am.amname as \"%s\"",
+
gettext_noop("Access Method"));
I'm not sure if we should include showViews, I had seen that the
access method was not getting selected for view.
Regards,
Vignesh
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Jaime Casanova | 2020-07-05 04:17:56 | Re: Built-in connection pooler |
Previous Message | vignesh C | 2020-07-05 00:59:04 | Re: Cleanup - Removed unused function parameter in reorder buffer & parallel vacuum |