Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hNg0c-0002Vc-OE for pgsql-hackers@arkaria.postgresql.org; Mon, 06 May 2019 15:58:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hNg0b-00065P-2Y for pgsql-hackers@arkaria.postgresql.org; Mon, 06 May 2019 15:58:29 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hNg0a-00064N-N0 for pgsql-hackers@lists.postgresql.org; Mon, 06 May 2019 15:58:28 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hNg0U-0008JE-8v for pgsql-hackers@postgresql.org; Mon, 06 May 2019 15:58:27 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x46FwIet016690; Mon, 6 May 2019 11:58:18 -0400 From: Tom Lane To: Rafia Sabih cc: Justin Pryzby , PostgreSQL-development Subject: Re: make \d pg_toast.foo show its indices In-reply-to: References: <20190422154902.GH14223@telsasoft.com> <20190503142721.GC3925@telsasoft.com> Comments: In-reply-to Rafia Sabih message dated "Mon, 06 May 2019 09:13:52 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <16688.1557158298.1@sss.pgh.pa.us> Date: Mon, 06 May 2019 11:58:18 -0400 Message-ID: <16689.1557158298@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Rafia Sabih writes: > On Fri, 3 May 2019 at 16:27, Justin Pryzby wrote: >> Thanks - what about also showing the associated non-toast table ? > 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. Possibly it is useful in the other direction as Justin suggests. Not sure though --- generally, if you're looking at a specific toast table, you already know which table is its parent. But maybe confirmation is a good thing. 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. regards, tom lane