From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Only owners can ANALYZE tables...seems overly restrictive |
Date: | 2016-02-29 16:58:24 |
Message-ID: | 56D478B0.2020405@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 02/29/2016 05:31 AM, Stephen Frost wrote:
> * David G. Johnston (david(dot)g(dot)johnston(at)gmail(dot)com) wrote:
>> Given the amount of damage a person with write access to a table can get
>> into it seems pointless to not allow them to analyze the table after their
>> updates - since best practices would say that normal work with a table
>> should not be performed by an owner.
>>
>> I should the check for whether a given user can or cannot analyze a table
>> should be whether the user has INSERT, UPDATE, or DELETE privileges.
>
> Realistically, ANALYZE is a background/maintenance task that autovacuum
> should be handling for you.
Incorrect. That would be autoanalyze and although they are similar they
are not the same. ANALYZE is used for a number of things, not the least
is query profiling.
Sincerely,
JD
--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2016-02-29 17:09:40 | Re: Only owners can ANALYZE tables...seems overly restrictive |
Previous Message | Albe Laurenz | 2016-02-29 16:27:17 | Re: Only owners can ANALYZE tables...seems overly restrictive |