From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | 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:14:30 |
Message-ID: | CAKFQuwaT0udU_htnavvKjS1z1hQKEevc2hdj1LyikrrqK=T9Sg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jul 18, 2018 at 12:55 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> regression=# \d tbl_include_reg_idx
> Index "public.tbl_include_reg_idx"
> Column | Type | Key | Definition
> --------+---------+------------------
> c1 | integer | t | c1
> c2 | integer | t | c2
> c3 | integer | f | c3
> c4 | box | f | c4
> btree, for table "public.tbl_include_reg"
>
+1 for the additional column indicating whether the column is being
treated as key data or supplemental included data.
-1 for printing a boolean t/f; would rather spell it out:
CASE WHEN "Key" THEN 'Key' ELSE 'Included' END AS "Data"
We're not hurting for horizontal space here and in any case I'd rather save
others the eye strain of having to distinguish between lowercase "f" and
"t".
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Fabien COELHO | 2018-07-18 20:15:30 | Re: Make foo=null a warning by default. |
Previous Message | Tom Lane | 2018-07-18 20:05:39 | Re: Background worker/idle sessions and caching |