Re: psql's \d versus included-index-column feature
| От | David G. Johnston |
|---|---|
| Тема | Re: psql's \d versus included-index-column feature |
| Дата | |
| Msg-id | CAKFQuwaT0udU_htnavvKjS1z1hQKEevc2hdj1LyikrrqK=T9Sg@mail.gmail.com обсуждение исходный текст |
| Ответ на | psql's \d versus included-index-column feature (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: psql's \d versus included-index-column feature
Re: psql's \d versus included-index-column feature |
| Список | pgsql-hackers |
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.
В списке pgsql-hackers по дате отправления: