David G. Johnston wrote: >>>> In a production environment you don't want a user to change your table >>>> statistics. >>>> >>>> They could just set default_statistics_target to something stupid, >>>> run ANALYZE and wreck the statistics for everyone. >>>> And then come back to the DBA and complain that things don't work. >>> Setting default_statistics_target and running ANALYZE are two entirely different things. >> Setting default_statistics_target affects the statistics computed by ANALYZE, >> so I cannot follow you here. > Just because I can run ANALYZE doesn't mean I should be able to update the statistic targets. While > the features are related the permissions are not. See http://www.postgresql.org/docs/current/static/planner-stats.html "The amount of information stored in pg_statistic by ANALYZE, in particular the maximum number of entries in the most_common_vals and histogram_bounds arrays for each column, can be set on a column-by-column basis using the ALTER TABLE SET STATISTICS command, or globally by setting the default_statistics_target configuration variable." Yours, Laurenz Albe -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
