| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: psql's \d versus included-index-column feature |
| Date: | 2018-07-18 21:05:44 |
| Message-ID: | 20180718210544.ynej3c6oos45u5t7@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2018-Jul-18, Tom Lane wrote:
> 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 think "Key: no" is a bit obscure -- using "included" is a bit more
self-documenting and lends better to documentation searches.
> I'd be OK with "Key"/"Included" as the values if someone can
> propose an on-point column header to go with those.
"Role"?
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2018-07-18 21:12:15 | Re: GiST VACUUM |
| Previous Message | Heikki Linnakangas | 2018-07-18 21:03:12 | Re: [HACKERS] Re: [COMMITTERS] pgsql: Remove pgbench "progress" test pending solution of its timing is (fwd) |