| From: | "David Wilson" <david(dot)t(dot)wilson(at)gmail(dot)com> |
|---|---|
| To: | Justin <justin(at)emproshunts(dot)com> |
| Cc: | mark <markkicks(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: select query takes 13 seconds to run with index |
| Date: | 2008-05-27 00:09:30 |
| Message-ID: | e7f9235d0805261709k638dbb23jef43b8fe62861fc7@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-performance |
On Mon, May 26, 2008 at 7:26 PM, Justin <justin(at)emproshunts(dot)com> wrote:
> The estimate is way off, when was the last time Vaccum was on the table?
I'm going to second this- run "ANALYZE pokes;" and then test the query
again; I'll bet you'll get much better results.
It's not the VACUUM that matters so much as the ANALYZE, and it
definitely needs to be done on occasion if you're adding a lot of
records. Do you have the autovacuum daemon running? (And if not, why
not?)
--
- David T. Wilson
david(dot)t(dot)wilson(at)gmail(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin | 2008-05-27 00:13:54 | Re: select query takes 13 seconds to run with index |
| Previous Message | Justin | 2008-05-27 00:05:20 | Re: select query takes 13 seconds to run with index |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin | 2008-05-27 00:13:54 | Re: select query takes 13 seconds to run with index |
| Previous Message | Justin | 2008-05-27 00:05:20 | Re: select query takes 13 seconds to run with index |