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

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: psql's \d versus included-index-column feature
Date: 2018-07-18 20:26:32
Message-ID: 20180718202632.i6lsh3dlzj6ygury@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2018-07-18 20:29:36 Re: [HACKERS] Re: [COMMITTERS] pgsql: Remove pgbench "progress" test pending solution of its timing is (fwd)
Previous Message Fabien COELHO 2018-07-18 20:15:30 Re: Make foo=null a warning by default.