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 1hO22l-0008Mn-FG for pgsql-hackers@arkaria.postgresql.org; Tue, 07 May 2019 15:30:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hO22j-00055v-TH for pgsql-hackers@arkaria.postgresql.org; Tue, 07 May 2019 15:30:09 +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 1hO22j-00052w-GA for pgsql-hackers@lists.postgresql.org; Tue, 07 May 2019 15:30:09 +0000 Received: from tamriel.snowman.net ([2001:470:e38f::11]) by makus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hO22h-00067a-2C for pgsql-hackers@postgresql.org; Tue, 07 May 2019 15:30:08 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id 946E65F79F; Tue, 7 May 2019 11:30:06 -0400 (EDT) Date: Tue, 7 May 2019 11:30:06 -0400 From: Stephen Frost To: Tom Lane Cc: Rafia Sabih , Justin Pryzby , PostgreSQL-development Subject: Re: make \d pg_toast.foo show its indices Message-ID: <20190507153006.GI6197@tamriel.snowman.net> References: <20190422154902.GH14223@telsasoft.com> <20190503142721.GC3925@telsasoft.com> <16689.1557158298@sss.pgh.pa.us> <20190507151600.GH6197@tamriel.snowman.net> <30641.1557242690@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="VOKQOYFLHSCzVt/O" Content-Disposition: inline In-Reply-To: <30641.1557242690@sss.pgh.pa.us> User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --VOKQOYFLHSCzVt/O Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Greetings, * Tom Lane (tgl@sss.pgh.pa.us) wrote: > Stephen Frost writes: > > * Tom Lane (tgl@sss.pgh.pa.us) wrote: > >> Rafia Sabih writes: > >>> IMHO, what makes more sense is to show the name of associated toast > >>> table in the \dt+ of the normal table. >=20 > >> I'm not for that: it's useless information in at least 99.44% of cases. >=20 > > 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: > > =3D> \d comments > > Table "public.comments" (50788) >=20 > 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 --VOKQOYFLHSCzVt/O Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJc0aR+AAoJEO1sijiDR2RVKawP+QHQRs2LAryZCY//NBWZxep2 ZinS3l2tT52uGzH+pSRm5GQynhllUIKARSEQDQYEQRpUlCgGXDfZY91pv/6gFk6t idMsegjW5xLxVWMOso0WjuAwnFoEe2ReqS+b2pvERx/tkbd0/mvoQ0l+EFF/2w4B 7cqlHZ7VXRuMPIT31qk6JpN8C3UArGEzLvYRY2tfs5PHWXHbaHwd9I1XAQVg5bKV 1QWHq0CFpFSBBULn8Z8Ue2zxbcGV37H5J+djZqdD9Hsk3I3Mt6swARo0dj+FDeP8 J9+s8RLjIajmBqr1kFbX0Wx8ix5X60ZyAVVOqeO5mjNh3btxR88rq6w+5h5Vdma7 Om4qa23ukF+bFD7YEP5XL7d7NUIMUavEXY0+M6seT5UQJ8pDujN1rvUB+IAcFfCn 6czbw0fNq6FInlpX1lZxuZpivbarBMBTdgKxRn4vpRH5tsM9uyepjHtOax2FrJtC NXCKURIGNHlJHgt1u1RXsqhC5ecrhnJi8YAx3j5UmLvCfLUIgUuAbHqkgVImY92o r1vOmSMUxXI58HAIWME3RLgry5upuYr9rNBPQ6OZn9Tje13hGX6poFxKYFgQWiFm 86+ReDHf6Z7fLM41lGRF98iz0HtWx2QpiGtRKkLdtierSv5tH9nvFWlVsGBNzUMq qchycQK26XUBL70IlY2i =bBpe -----END PGP SIGNATURE----- --VOKQOYFLHSCzVt/O--