From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(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:08:38 |
Message-ID: | 56D48926.7050108@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 02/29/2016 10:06 AM, Alvaro Herrera wrote:
> 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.
Actually I am not but I can see how it wasn't clear.
>
> 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).
One item that can be helpful from ANALYZE (not EXPLAIN ANALYZE) is
modifying the statistics via SET, running Analyze and see if the query
improves. You can then determine where best to set those statistics
(usually ALTER TABLE).
Sincerely,
JD
--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2016-02-29 18:31:29 | Re: multicolumn index and setting effective_cache_size using human-readable-numbers |
Previous Message | Alvaro Herrera | 2016-02-29 18:06:01 | Re: Only owners can ANALYZE tables...seems overly restrictive |