Re: Only owners can ANALYZE tables...seems overly restrictive

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(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 18:06:01
Message-ID: 20160229180601.GA284094@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Joshua D. Drake wrote:
> On 02/29/2016 05:31 AM, Stephen Frost wrote:

> >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.

I think you are confusing ANALYZE with EXPLAIN ANALYZE.

I am not aware of any way in which ANALYZE is different from what you
call "autoanalyze" (which is really just an autovacuum-invoked ANALYZE
and for which we don't have any specific term).

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Joshua D. Drake 2016-02-29 18:08:38 Re: Only owners can ANALYZE tables...seems overly restrictive
Previous Message Geoff Winkless 2016-02-29 18:05:37 Re: multicolumn index and setting effective_cache_size using human-readable-numbers