| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-06 17:52:23 |
| Message-ID: | CA+TgmoZ8YdV4oJ49obi1au_Jn5TgH8pTGvyS+dHkMjYxG8ZgrA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, May 6, 2019 at 12:26 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> I'm not convinced by that. I've certainly many a time wrote queries
> against pg_class to figure out which relation a toast table belongs
> to. E.g. after looking at the largest relations in the system, looking
> at pg_stat_*_tables, after seeing an error in the logs, etc.
+1. I think it would be great for \d on the TOAST table to show this
information.
> > That seems off-topic for this thread though. I agree with the
> > stated premise that \d on a toast table should show all the same
> > information \d on a regular table would.
>
> +1
That premise seems like a good one, too.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2019-05-06 17:56:47 | Naming of pg_checksums |
| Previous Message | Robert Haas | 2019-05-06 17:51:33 | Re: Unhappy about API changes in the no-fsm-for-small-rels patch |