From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Re: proposal - psql: possibility to specify sort for describe commands, when size is printed |
Date: | 2017-03-30 15:49:46 |
Message-ID: | CAFj8pRC_N5Pg2pcQwchL_9MRL=LdEKWB=rxPgArPdJXZSGWVLw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>
>
>>>>
>>>> This proposal was here already - maybe two years ago. The psql command
>>>> parser doesn't allow any complex syntax - more - the more parameters in one
>>>> psql commands is hard to remember, hard to read.
>>>>
>>>
>>> Could you please provide a link to this discussion. Probably working
>>> with multiple parameters in psql commands require some rework, but that's
>>> definitely doable.
>>>
>>
>> http://grokbase.com/t/postgresql/pgsql-hackers/137nt5p6s0/
>> proposal-psql-show-longest-tables/oldest
>> https://www.postgresql.org/message-id/AANLkTikyaeJ0XdKDzxSvq
>> PE8kaRRTiUQJQHwNJ8ecN2W(at)mail(dot)gmail(dot)com
>>
>
> I took a look to these threads, but I didn't find place where difficulties
> of adding extra arguments to psql commands are pointed.
> Could you, please, point particular messages about it?
>
I am sorry - maybe my memory doesn't serve well
Pavel
>
> ------
> Alexander Korotkov
> Postgres Professional: http://www.postgrespro.com
> The Russian Postgres Company
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2017-03-30 15:50:59 | Re: Patch: Write Amplification Reduction Method (WARM) |
Previous Message | Robert Haas | 2017-03-30 15:49:21 | Re: [POC] A better way to expand hash indexes. |