| From: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
|---|---|
| To: | "Shinoda, Noriyoshi (PN Japan FSIP)" <noriyoshi(dot)shinoda(at)hpe(dot)com>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, Tatsuro Yamada <tatsuro(dot)yamada(dot)tf(at)nttcom(dot)co(dot)jp> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, 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: | 2021-01-17 02:01:34 |
| Message-ID: | d876a1e3-9a6c-712e-7ab8-3dfa8a4cac1e@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/17/21 2:41 AM, Shinoda, Noriyoshi (PN Japan FSIP) wrote:
> Hi, hackers.
>
> I tested this committed feature.
> It doesn't seem to be available to non-superusers due to the inability to access pg_statistics_ext_data.
> Is this the expected behavior?
>
Hmmm, that's a good point. Bummer we haven't noticed that earlier.
I wonder what the right fix should be - presumably we could do something
like pg_stats_ext (we can't use that view directly, because it formats
the data, so the sizes are different).
But should it list just the stats the user has access to, or should it
list everything and leave the inaccessible fields NULL?
regards
--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-01-17 02:12:03 | Calculation of relids (pull_varnos result) for PlaceHolderVars |
| Previous Message | Tomas Vondra | 2021-01-17 01:43:10 | Re: Why does create_gather_merge_plan need make_sort? |