From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Rafia Sabih <rafia(dot)pghackers(at)gmail(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: make \d pg_toast.foo show its indices |
Date: | 2019-05-07 15:30:06 |
Message-ID: | 20190507153006.GI6197@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Greetings,
* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> Stephen Frost <sfrost(at)snowman(dot)net> writes:
> > * Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> >> Rafia Sabih <rafia(dot)pghackers(at)gmail(dot)com> writes:
> >>> IMHO, what makes more sense is to show the name of associated toast
> >>> table in the \dt+ of the normal table.
>
> >> I'm not for that: it's useless information in at least 99.44% of cases.
>
> > I don't think I'd put it in \dt+, but the toast table is still
> > pg_toast.pg_toast_{relOid}, right? What about showing the OID of the
> > table in the \d output, eg:
> > => \d comments
> > Table "public.comments" (50788)
>
> Not unless you want to break every regression test that uses \d.
> Instability of the output is also a reason not to show the
> toast table's name in the parent's \d[+].
So we need a way to turn it off. That doesn't seem like it'd be hard to
implement and the information is certainly quite useful.
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2019-05-07 15:41:47 | Re: New EXPLAIN option: ALL |
Previous Message | Tom Lane | 2019-05-07 15:24:50 | Re: make \d pg_toast.foo show its indices |