Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] Re: proposal - psql: possibility to specify sort fordescribe commands, when size is printed - Mailing list pgsql-hackers

From Alexander Korotkov
Subject Re: [HACKERS] Re: proposal - psql: possibility to specify sort fordescribe commands, when size is printed
Date
Msg-id CAPpHfdsAyaE6AX_n7wE4jfxiO_JoD0+Ne=LGVbx67qZoiYp3zA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Re: proposal - psql: possibility to specify sort fordescribe commands, when size is printed  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: [HACKERS] Re: proposal - psql: possibility to specify sort fordescribe commands, when size is printed  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
Tree view
On Fri, Mar 10, 2017 at 5:10 PM, Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote:
On 2/24/17 16:32, Pavel Stehule wrote:
>     set EXTENDED_DESCRIBE_SORT size_desc
>     \dt+
>     \l+
>     \di+
>
>     Possible variants: schema_table, table_schema, size_desc, size_asc

I can see this being useful, but I think it needs to be organized a
little better.

Sort key and sort direction should be separate settings.
 
I agree.

I'm not sure why we need to have separate settings to sort by schema
name and table name.

I think sorting by schema name, object name makes sense for people, who have objects of same name in different schemas.

------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
 

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] Write Ahead Logging for Hash Indexes
Next
From: Kevin Grittner
Date:
Subject: Re: [HACKERS] GSOC Introduction / Eliminate O(N^2) scaling fromrw-conflict tracking in serializable transactions