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 1hONZF-0002il-SB for pgsql-hackers@arkaria.postgresql.org; Wed, 08 May 2019 14:29:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hONZC-0003w7-DG for pgsql-hackers@arkaria.postgresql.org; Wed, 08 May 2019 14:29:06 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hONZC-0003tA-3I for pgsql-hackers@lists.postgresql.org; Wed, 08 May 2019 14:29:06 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hONZ6-0000JD-Qw for pgsql-hackers@postgresql.org; Wed, 08 May 2019 14:29:04 +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 x48ESuAC025755; Wed, 8 May 2019 10:28:56 -0400 From: Tom Lane To: Robert Haas cc: Stephen Frost , Rafia Sabih , Justin Pryzby , PostgreSQL-development Subject: Re: make \d pg_toast.foo show its indices In-reply-to: References: <20190503142721.GC3925@telsasoft.com> <16689.1557158298@sss.pgh.pa.us> <20190507151600.GH6197@tamriel.snowman.net> <30641.1557242690@sss.pgh.pa.us> <20190507153006.GI6197@tamriel.snowman.net> <20190507204809.GM6197@tamriel.snowman.net> <3433.1557265781@sss.pgh.pa.us> <20190507220329.GN6197@tamriel.snowman.net> Comments: In-reply-to Robert Haas message dated "Wed, 08 May 2019 10:18:13 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <25753.1557325736.1@sss.pgh.pa.us> Date: Wed, 08 May 2019 10:28:56 -0400 Message-ID: <25754.1557325736@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Robert Haas writes: > I think it's unjustifiable to show this in \d output. But maybe in > \d+ output it could be justified, or perhaps in the \d++ which I seem > to recall Alvaro proposing someplace recently. Yeah, if we're going to do that (show a table's toast table) I would want to bury it in \d++ or some other not-currently-used notation. regards, tom lane