Re: psql's \d versus included-index-column feature

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: psql's \d versus included-index-column feature
Дата
Msg-id 24241.1531946776@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: psql's \d versus included-index-column feature  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Ответы Re: psql's \d versus included-index-column feature  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Список pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> On 2018-Jul-18, David G. Johnston wrote:
>> -1 for printing a boolean t/f; would rather spell it out:
>> 
>> CASE WHEN "Key" THEN 'Key' ELSE 'Included' END AS "Data"

> +1

I can sympathize with the eyestrain argument against t/f, but the
above doesn't seem like an improvement --- in particular, "Data"
as the column header seems quite content-free.  My counterproposal
is to keep "Key" as the header and use "Yes"/"No" as the values.

I'd be OK with "Key"/"Included" as the values if someone can
propose an on-point column header to go with those.

            regards, tom lane


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

Предыдущее
От: Jeremy Finzel
Дата:
Сообщение: Re: Background worker/idle sessions and caching
Следующее
От: Heikki Linnakangas
Дата:
Сообщение: Re: [HACKERS] Re: [COMMITTERS] pgsql: Remove pgbench "progress" testpending solution of its timing is (fwd)