Re: Re: proposal - psql: possibility to specify sort for describe commands, when size is printed

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>
Cc: 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-09-21 08:27:32
Message-ID: CAFj8pRAiVcQzj+LFTuDV=PsM+r09imsH8zHveKAu4StE=mo5UQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2017-09-21 10:19 GMT+02:00 Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>:

> On Thu, Sep 21, 2017 at 1:53 AM, Peter Eisentraut <
> peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>
>> On 9/8/17 00:13, Pavel Stehule wrote:
>> > I am sending rebased patch
>> >
>> > rebased again + fix obsolete help
>>
>> Why are the variables called VERBOSE_SORT_* ? What is verbose about them?
>
>
> I assume Pavel called them so, because they are working only for "verbose"
> mode of command. I.e. they are working for \dt+ not \dt.
> However, in \dt 2 of 3 sorting modes might work: schema_name and
> name_schema. Thus, I think it worths enabling these variables for "non
> verbose" mode of commands too.
>

yes. It was designed for + commands only. Can be enhanced to all commands -
then VERBOSE prefix should be removed - not sure if it is necessary. For me
interesting different order than default is only in verbose mode.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2017-09-21 08:27:47 Re: compress method for spgist - 2
Previous Message Fabien COELHO 2017-09-21 08:23:45 Re: pgbench: Skipping the creating primary keys after initialization