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

From Peter Eisentraut
Subject Re: [HACKERS] Re: proposal - psql: possibility to specify sort fordescribe commands, when size is printed
Date
Msg-id 7e0a9c97-d48e-01d5-6437-b275e7dfc594@2ndquadrant.com
Whole thread Raw
In response to [HACKERS] Re: proposal - psql: possibility to specify sort for describecommands, when size is printed  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: [HACKERS] Re: proposal - psql: possibility to specify sort fordescribe commands, when size is printed  (Stephen Frost <sfrost@snowman.net>)
Re: [HACKERS] Re: proposal - psql: possibility to specify sort fordescribe commands, when size is printed  (Alexander Korotkov <a.korotkov@postgrespro.ru>)
Re: [HACKERS] Re: proposal - psql: possibility to specify sort fordescribe commands, when size is printed  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
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'm not sure why we need to have separate settings to sort by schema
name and table name.  But if we do, then we should support that for all
object types.  I think maybe that's something we shouldn't get into
right now.

So I would have one setting for sort key = {name|size} and on for sort
direction = {asc|desc}.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: [HACKERS] PATCH: psql show index with type info
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Automatic cleanup of oldest WAL segments withpg_receivexlog