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 1hNgZ7-0004HY-Mi for pgsql-hackers@arkaria.postgresql.org; Mon, 06 May 2019 16:34:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hNgZ5-0007Mp-8I for pgsql-hackers@arkaria.postgresql.org; Mon, 06 May 2019 16:34:07 +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 1hNgZ4-0007Mi-S4 for pgsql-hackers@lists.postgresql.org; Mon, 06 May 2019 16:34:07 +0000 Received: from mail-qt1-x844.google.com ([2607:f8b0:4864:20::844]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hNgZ1-0000gt-KU for pgsql-hackers@postgresql.org; Mon, 06 May 2019 16:34:05 +0000 Received: by mail-qt1-x844.google.com with SMTP id j6so15455601qtq.1 for ; Mon, 06 May 2019 09:34:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=lYCkWAYgNF565Rrp3fpbURUAueF3BTS/a2ukHoTaOhI=; b=xMTB7Bto2LajmtvjRA0j4DpnCEOQqWXCM3L9pW1Nkv+tTZUiG+9Xgf5EMiFL6mi9D6 f3Z/hB6Yp6Kmz/TJ0cumss3Zw54sWJ7ODIiwpBggA0xfZsKt6u1e4wyJKmp8xZfPqopC O8otOk3XDx3smySzJEiijj3PtIbLGZEXSuenbYZ3IOPvIXJXb1mzyo2sCOipbkfx6rnv nze9cooenGxa2H5J5hkzZis/zcNbOVpHSJd2Uzz+YZ2t2EvsgKoFeAi294zWHbDu/epA KLAfiK+C9eM85uE0QDHyVHEjTChmq9XAE+SD1tuWFfAXYUPRXdccpmBhqeN9KJmd6k6E GpSA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=lYCkWAYgNF565Rrp3fpbURUAueF3BTS/a2ukHoTaOhI=; b=IN3j4ixpkI/KP+758DcmhNGIJsGgD6+XiS8Htujik8/mN9gG4BOP8BAzDyAzcerBhj qLugDNQhnSZtKBsdbVlYlO2XHULIEyhHusxiGK8tqeebbQZrTuTCuph89x85kSkRH9WB Lfu/8ZSTFrW4OR6/ezZLrDakBtD/Y7opKJgbPIuSJ3S9aiewasrmgCycBB8CsC+1rBgG 2ylzpDVlczc2FyZrfnrhGJO4nEfnWrOldxufDHD3fk0s7J3pAcZGnwgppuNOlfvtSWvF R4AoDNZwgnYHZcKUZ5JYfo9pm8r7Ztjro+b64nFETym1o8grXFpoX+hCRsnAj/IwKvff taBw== X-Gm-Message-State: APjAAAWBDQ0VtvR0cJaoQVxi9NoI+VnMqWQsaY6Z4KenuiWnIkpA749d se3phvdKxW3BmrTW2n6qyh9z2w== X-Google-Smtp-Source: APXvYqzdF2tFO1H3D1efTRd2Y4BNv3ps5WwEBh02z1hNg/wn2X36ClIdFov5+KhFwH0Td/kGkHyMjw== X-Received: by 2002:ac8:3613:: with SMTP id m19mr829004qtb.351.1557160442851; Mon, 06 May 2019 09:34:02 -0700 (PDT) Received: from nimloth.alvh.no-ip.org ([190.121.29.3]) by smtp.gmail.com with ESMTPSA id j5sm6253695qtb.30.2019.05.06.09.34.01 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 06 May 2019 09:34:02 -0700 (PDT) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id 5FA301239A8; Mon, 6 May 2019 12:33:59 -0400 (-04) Date: Mon, 6 May 2019 12:33:59 -0400 From: Alvaro Herrera To: Justin Pryzby Cc: Rafia Sabih , PostgreSQL-development Subject: Re: make \d pg_toast.foo show its indices ; and, \d toast show its main table Message-ID: <20190506163359.GA29291@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20190506162251.GN3925@telsasoft.com> User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2019-May-06, Justin Pryzby wrote: > Perhaps ... but TOAST is an implementation detail, and I think it should rarely > be important to know the toast table for a given table. I'm with Andres -- while it's admittedly a rare need, it is a real one. Sometimes I wish for \d++ which would display internal details too obscure to show in the regular \d+, such as the toast table name. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services