| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
| Cc: | 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 16:18:09 |
| Message-ID: | 20200831161809.GA31337@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-Aug-31, Tomas Vondra wrote:
> I wonder if trying to list info about all stats from the statistics
> object in a single line is necessary. Maybe we should split the info
> into one line per statistics, so for example
>
> CREATE STATISTICS s (mcv, ndistinct, dependencies) ON ...
>
> would result in three lines in the \dX output. The statistics name would
> identify which lines belong together, but other than that the pieces are
> mostly independent.
Yeah, that's what I'm suggesting. I don't think we need to repeat the
name/definition for each line though.
It might be useful to know how does pspg show a single entry that's
split in three lines, though.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2020-08-31 16:19:52 | Re: Ideas about a better API for postgres_fdw remote estimates |
| Previous Message | Bruce Momjian | 2020-08-31 16:14:55 | Re: Ideas about a better API for postgres_fdw remote estimates |