Date: Sun, 30 Aug 2020 00:54:36 +0200
From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Tatsuro Yamada <tatsuro.yamada.tf@nttcom.co.jp>,
	Julien Rouhaud <rjuju123@gmail.com>,
	Pavel Stehule <pavel.stehule@gmail.com>,
	PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: list of extended statistics on psql
Message-ID: <20200829225436.atuttqilrcgppqio@development>
References: <20200829215458.ca6pnchavgfhs2pf@development>
 <20200829224347.GA16787@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
In-Reply-To: <20200829224347.GA16787@alvherre.pgsql>
Precedence: bulk

On Sat, Aug 29, 2020 at 06:43:47PM -0400, Alvaro Herrera wrote:
>On 2020-Aug-29, Tomas Vondra wrote:
>
>> But if we want the
>> output to show both what was requested and which types were actually
>> built, that'll effectively double the number of columns needed :-(
>
>I was thinking it would be one column per type showing either disabled or enabled
>or built.  But another idea is to show one type per line that's at least
>enabled.
>
>> Also, it might be useful to show the size of the statistics built, just
>> like we show for \d+ etc.
>
>\dX+  I  suppose?
>

Right. I've only used \d+ as an example of an existing command showing
sizes of the objects.

regards

--
Tomas Vondra                  http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services