| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Isaac Morland <isaac(dot)morland(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Documentation clarification re: ANALYZE |
| Date: | 2019-08-07 21:31:45 |
| Message-ID: | CAKFQuwY8f_6bFi1Hfq5vWU8jFVSOshDCnbjtdfi-V5nRsSK+=w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 7, 2019 at 2:14 PM Isaac Morland <isaac(dot)morland(at)gmail(dot)com>
wrote:
> I'm looking at https://www.postgresql.org/docs/current/sql-analyze.html,
> where it says “Without a table_and_columns list, ANALYZE processes every
> table and materialized view in the current database that the current user
> has permission to analyze.”.
>
> I don’t believe there is a separate “analyze” permission, so which tables
> is this? Tables owned by the user? Ones where it can insert/update/delete?
> Ones where it can select?
>
Owners only - at least in previous releases. I don't recall whether the
addition of new roles to cover subsets of administrative privileges ever
was extended to cover vacuum/analyze but I do not think it has.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Isaac Morland | 2019-08-07 21:42:23 | Re: Documentation clarification re: ANALYZE |
| Previous Message | Tom Lane | 2019-08-07 21:22:01 | Re: no default hash partition |