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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Oleksandr Shulgin <oleksandr(dot)shulgin(at)zalando(dot)de>
Cc: Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: psql's \d versus included-index-column feature
Date: 2018-07-19 15:11:00
Message-ID: 23118.1532013060@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Oleksandr Shulgin <oleksandr(dot)shulgin(at)zalando(dot)de> writes:
> I don't think there is an established practice on how to display this sort
> of info, but I see that both styles already exist, namely:

> =# \dL
> List of languages
> Name | Owner | Trusted | Description
> ------------+----------+---------+------------------------------
> plpgsql | postgres | t | PL/pgSQL procedural language
> plproxy | postgres | f |
> ...

> and

> =# \dC
> List of casts
> Source type | Target type | Function
> | Implicit?
> -----------------------------+-----------------------------+--------------------+---------------
> abstime | date | date
> | in assignment
> abstime | integer | (binary
> coercible) | no
> abstime | timestamp without time zone | timestamp
> | yes
> ...

> I like the second option more, for readability reasons and because it is
> easier to extend if ever needed.

> 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?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next 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
Previous Message a.bykov 2018-07-19 14:24:10 Re: pgbench-ycsb