| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | "Paul McKay" <paul_mckay(at)clearwater-it(dot)co(dot)uk>, "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Slow query performance on large table |
| Date: | 2003-03-04 17:14:44 |
| Message-ID: | 200303040914.44390.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Paul,
> Index Scan using idx_measurement_assessment on measurement
> (cost=0.00..34668.61 rows=261 width=8) (actual time=26128.07..220584.69
> rows=503 loops=1)
> Total runtime: 220587.06 msec
These query results say to me that you need to do both a VACUUM FULL and a
REINDEX on this table. The 26-second delay before returning the first row
says "table/index with lots of dead pages" to me.
For the future, you should consider dramatically increasing your FSM settings
and working a regular VACUUM FULL and REINDEX into your maintainence jobs.
--
Josh Berkus
Aglio Database Solutions
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul McKay | 2003-03-04 17:19:03 | Re: Slow query performance on large table |
| Previous Message | Robert Treat | 2003-03-04 17:02:29 | Re: Slow query performance on large table |