From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Tomas Vondra <tomas(dot)vondra(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 14:58:11 |
Message-ID: | 3959104.1598885891@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Kasahara Tatsuhito | 2020-08-31 15:03:08 | Re: Get memory contexts of an arbitrary backend process |
Previous Message | Alvaro Herrera | 2020-08-31 14:28:38 | Re: list of extended statistics on psql |