On Mon, Aug 31, 2020 at 10:58:11AM -0400, Tom Lane wrote:
>Alvaro Herrera <alvherre@2ndquadrant.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
