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

Поиск
Список
Период
Сортировка
От Pavel Stehule
Тема Re: [HACKERS] Re: proposal - psql: possibility to specify sort fordescribe commands, when size is printed
Дата
Msg-id CAFj8pRCoOym8+qsqHW6AHD9JwoQj8WWtU=4hrjD688i13=bPoA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] Re: proposal - psql: possibility to specify sort fordescribe commands, when size is printed  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Ответы Re: [HACKERS] Re: proposal - psql: possibility to specify sort fordescribe commands, when size is printed  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Список pgsql-hackers


2017-09-21 15:30 GMT+02:00 Peter Eisentraut <peter.eisentraut@2ndquadrant.com>:
On 9/21/17 04:27, Pavel Stehule wrote:
> 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.

I see where you are coming from, but there is no association in the
existing UI that equates "+" to the word "verbose".  I think just
removing the verbose prefix and applying the sorting behavior in all
cases should be easier to explain and implement.

I though about it - but I am not sure if one kind of these variables is practical.

if I don't need a size, then sort by schema, name is ok (I didn't need any else ever). With only one kind of these variables, this setting is common - what is not practical.

I need sort by size in verbose mode (where size is visible) in 100% - so it will be saved to psqlrc. And when size will be invisible, then sort by size is not practical, and can be messy (because size is not visible).

So I don't think so removing VERBOSE prefix is a good idea - or we should to do different design (have not a idea how)

Regards

Pavel


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

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Dilip Kumar
Дата:
Сообщение: Re: [HACKERS] Effect of changing the value for PARALLEL_TUPLE_QUEUE_SIZE
Следующее
От: Jeff Janes
Дата:
Сообщение: Re: [HACKERS] SCRAM in the PG 10 release notes