Re: Auto ANALYZE criteria - Mailing list pgsql-performance

From Joe Miller
Subject Re: Auto ANALYZE criteria
Date
Msg-id AANLkTimqzLsA24-SED+ywHL6E=jXt_dcfu=c5=YN7XWR@mail.gmail.com
Whole thread Raw
In response to Re: Auto ANALYZE criteria  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Auto ANALYZE criteria
List pgsql-performance
Thanks for fixing the docs, but if that's the case, I shouldn't be
seeing the behavior that I'm seeing.

Should I flesh out this test case a little better and file a bug?

Thanks,

Joe


On Tue, Sep 21, 2010 at 4:44 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Joe Miller <joe.d.miller@gmail.com> writes:
>> I was looking at the autovacuum documentation:
>> http://www.postgresql.org/docs/9.0/interactive/routine-vacuuming.html#AUTOVACUUM
>
>>    For analyze, a similar condition is used: the threshold, defined as:
>>    analyze threshold = analyze base threshold + analyze scale factor *
>> number of tuples
>>    is compared to the total number of tuples inserted or updated since
>> the last ANALYZE.
>
>> I guess that should be updated to read "insert, updated or deleted".
>
> Mph.  We caught the other places where the docs explain what the analyze
> threshold is, but missed that one.  Fixed, thanks for pointing it out.
>
>                        regards, tom lane
>

pgsql-performance by date:

Previous
From: Nikolai Zhubr
Date:
Subject: Index scan / Index cond limitation or ?
Next
From: Brandon Casci
Date:
Subject: help with understanding EXPLAIN