Re: list of extended statistics on psql

From: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tatsuro Yamada <tatsuro(dot)yamada(dot)tf(at)nttcom(dot)co(dot)jp>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: list of extended statistics on psql
Date: 2020-08-31 15:20:57
Message-ID: 20200831152057.t5kijt5uoww5zs5o@development
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Aug 31, 2020 at 10:58:11AM -0400, Tom Lane wrote:
>Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
>> If we do put each type in its own row -- at least "logical" row, say
>> string_agg(unnest(array_of_types), '\n') -- then we can put the size of each type
>> in a separate column with string_agg(unnest(array_of_sizes), '\n')
>
>> statname | definition | type | size
>> ----------+-----------------+--------------------------+-----------
>> someobj | (a, b) FROM tab | n-distinct: built | 2000 bytes
>> | func-dependencies: built | 4000 bytes
>> another | (a, c) FROM tab | n-distint: enabled | <null>
>
>I guess I'm wondering why the size is of such interest that we
>need it at all here.
>

I agree it may not be important enough. I did use it during development
etc. but maybe it's not something we need to include in this list (even
if it's just in the \dX+ variant).

regards

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2020-08-31 15:30:53 Re: list of extended statistics on psql
Previous Message Anastasia Lubennikova 2020-08-31 15:10:46 Re: REINDEX SCHEMA/DATABASE/SYSTEM weak with dropped relations