From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
Cc: | Georgios Kokolatos <gkokolatos(at)protonmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
Subject: | Re: v13: show extended stats target in \d |
Date: | 2020-09-09 22:16:35 |
Message-ID: | 20200909221635.GA29948@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2020-Sep-09, Justin Pryzby wrote:
> As for the discussion about a separator, I think maybe a comma is enough. I
> doubt anyone is going to think that you can get a valid command by prefixing
> this by "CREATE STATISTICS". Actually, it didn't even occur to me it was valid
> command without the stats target - after all, that's not true of indexes.
>
> + "public"."ab1_a_b_stats" (ndistinct, dependencies, mcv) ON a, b FROM ab1, STATISTICS 0
I vote to use a semicolon instead of comma, and otherwise +1.
> This revision only shows the stats target in verbose mode (slash dee plus).
I don't think this interferes enough with other stuff to relegate it to
the "plus" version, since it's not shown if default.
Tomas -- this needs to go in pg13, right?
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2020-09-09 22:22:30 | Re: v13: show extended stats target in \d |
Previous Message | Tom Lane | 2020-09-09 22:00:41 | Re: SIGQUIT handling, redux |