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

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: Oleksandr Shulgin <oleksandr(dot)shulgin(at)zalando(dot)de>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: psql's \d versus included-index-column feature
Date: 2018-07-19 15:44:10
Message-ID: CAKFQuwYrri_n5ONPer6Yy+VxhzPCADb77ewuOjGw6+z-mQc+aw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thursday, July 19, 2018, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

>
> > Given that the documentation refers to included columns as "non-key
> > columns", it seems natural to me to name the \d output column "Key?" and
> > use "yes/no" as the values.
>
> WFM, anyone want to argue against?
>

Works for me as well.

David J.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2018-07-19 17:28:36 Re: [COMMITTERS] pgsql: Give a better error message on invalid hostaddr option.
Previous Message R, Siva 2018-07-19 15:17:09 Re: Bug in gin insert redo code path during re-compression of empty gin data leaf pages