From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr> |
Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal - psql - show longest tables |
Date: | 2013-07-23 04:14:07 |
Message-ID: | CAFj8pRDc0ot-64RfRvLaTCp7wcQ5_ZpaDLkv3mmTBwWYBh5KLQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2013/7/22 Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>:
> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
>>> SELECT * from top5();
>
> $ TABLE top5; -- add a view on top of the SRF
>
>> you cannot use parameters - then I have to have prepared files like
>> top10, top20, ... what is not too friendly
>
> The SRF could be using custom GUCs so that you can parametrize it, or
> just even classic parameters…
>
> $ TABLE top(5); -- needs a patch to accept SRF here…
> $ TABLE top LIMIT 5;
>
> $ SET top.limit = 5;
> $ TABLE top;
>
It just not comfortable and it is not consistent with current psql
commands design.
In my proposal, you should to learn just char "s". I expect so every
body knows "\dt"
so
\dts 10
compare with:
$ TABLE top(5); -- needs a patch to accept SRF here…
$ TABLE top LIMIT 5;
Regards
Pavel
> Regards,
> --
> Dimitri Fontaine
> http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2013-07-23 04:18:27 | Re: proposal - psql - show longest tables |
Previous Message | Amit Langote | 2013-07-23 04:11:45 | maintenance_work_mem and CREATE INDEX time |