pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Oleksandr Shulgin <oleksandr.shulgin@zalando.de>
Cc: Alexander Korotkov <a.korotkov@postgrespro.ru>
Cc: David G. Johnston <david.g.johnston@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: psql's \d versus included-index-column feature
Date: Thu, 19 Jul 2018 11:11:00 -0400
Message-ID: <23118.1532013060@sss.pgh.pa.us> (raw)
In-Reply-To: <CACACo5Si9=k=jYodyRD9ykzBjSki2h6-=sbR-YSTYu6EpPKBXQ@mail.gmail.com>
References: <21724.1531943735@sss.pgh.pa.us>
	<CAKFQuwaT0udU_htnavvKjS1z1hQKEevc2hdj1LyikrrqK=T9Sg@mail.gmail.com>
	<CAPpHfdsz6M1VsQ82n1wWUf22QCKgLjgzXjyURrCi2Ad-atFUkw@mail.gmail.com>
	<CACACo5Si9=k=jYodyRD9ykzBjSki2h6-=sbR-YSTYu6EpPKBXQ@mail.gmail.com>

Oleksandr Shulgin <oleksandr.shulgin@zalando.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




view thread (9+ messages)  latest in thread

Message-ID: <23118.1532013060@sss.pgh.pa.us>
Permalink:  ../23118.1532013060@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/23118.1532013060@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, oleksandr.shulgin@zalando.de, a.korotkov@postgrespro.ru, david.g.johnston@gmail.com, pgsql-hackers@lists.postgresql.org
  Subject: Re: psql's \d versus included-index-column feature
  In-Reply-To: <23118.1532013060@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox