| From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "'David G(dot) Johnston *EXTERN*'" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | John R Pierce *EXTERN* <pierce(at)hogranch(dot)com>, "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 15:46:29 |
| Message-ID: | A737B7A37273E048B164557ADEF4A58B538045A3@ntex2010i.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
David G. Johnston wrote:
> On Mon, Feb 29, 2016 at 2:52 AM, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> wrote:
>> John R Pierce wrote:
>>> analyze has arguably fewer side effects, its a performance enhancement,
>>> its neither altering the schema or changing the data.
>> 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.
>>
>> We have a policy that users are not table owners, and with the
>> current behaviour we can be certain that any bad table statistics
>> are the fault of the DBA or wrong configuration.
> 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.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2016-02-29 16:13:49 | Re: Only owners can ANALYZE tables...seems overly restrictive |
| Previous Message | Stephen Frost | 2016-02-29 15:28:50 | Re: Only owners can ANALYZE tables...seems overly restrictive |