On 02/29/2016 05:31 AM, Stephen Frost wrote:
* David G. Johnston (david.g.johnston@xxxxxxxxx) 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.
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
