| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | <lionel(dot)duboeuf(at)boozter(dot)com>,<pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Almost infinite query -> Different Query Plan when changing where clause value |
| Date: | 2010-02-15 14:19:19 |
| Message-ID: | 4B790387020000250002F2CF@gw.wicourts.gov |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
lionel duboeuf wrote:
> Kevin Grittner a écrit :
>> I just reread your original email, and I'm not sure I understand
>> what you meant regarding VACUUM ANALYZE. If you run that right
>> beforehand, do you still get the slow plan for user 10?
> I confirm by executing manual "VACUUM ANALYZE" that the problem is
> solved. But what i don't understand is that i would expect
> autovacuum to do the job.
I think this is the crux of the issue. Boosting the
default_statistics_target or the statistics target for specific
columns might help, reducing autovacuum_analyze_scale_factor might
help, but I can't help wondering whether you inserted a large number
of rows for user 10 and then ran the query to select user 10 before
autovacuum had time to complete. Does that seem possible?
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2010-02-15 14:33:11 | Re: PostgreSQL on SMP Architectures |
| Previous Message | Yeb Havinga | 2010-02-15 11:11:23 | Re: Why primary key index are not using in joining? |