Re: proposal - psql - show longest tables - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: proposal - psql - show longest tables
Date
Msg-id CAFj8pRAQ1kom29nTgm1Htjaxe0jgFYEWHCt=zU8W2T66BY7Csw@mail.gmail.com
Whole thread Raw
In response to Re: proposal - psql - show longest tables  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
2013/7/23 Pavel Stehule <pavel.stehule@gmail.com>:
> 2013/7/22 Dimitri Fontaine <dimitri@2ndquadrant.fr>:
>> Pavel Stehule <pavel.stehule@gmail.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;

I know so psql commands looks strange, but after few years when I work
with other db, I am thinking so this (ingres design) was very
practical - we have almost all important informations after press two
or three keys. This has no any other database, and a few database copy
this interface from us - Vertica, Monetdb.

Regards

Pavel

>
> Regards
>
> Pavel
>
>> Regards,
>
>> --
>> Dimitri Fontaine
>> http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: proposal - psql - show longest tables
Next
From: David Fetter
Date:
Subject: Re: GSOC13 proposal - extend RETURNING syntax