| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Richard Huxton <dev(at)archonet(dot)com> |
| Cc: | soni de <soni(dot)de(at)gmail(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Rajesh Kumar Mallah <mallah(dot)rajesh(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Takes too long to fetch the data from database |
| Date: | 2006-04-11 13:45:36 |
| Message-ID: | 7301.1144763136@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Richard Huxton <dev(at)archonet(dot)com> writes:
> soni de wrote:
>> NOTICE: QUERY PLAN:
>> Sort (cost=17.13..17.13 rows=1 width=16) (actual time=619140.18..619140.29rows
>> =288 loops=1)
>> -> Index Scan using lan_pkey on lan (cost=0.00..17.12 rows=1 width=16)
>> (actual time=7564.44..619121.61 rows=288 loops=1)
>>
>> Total runtime: 619140.76 msec
> OK - there is clearly something wrong here when you take 10 minutes to
> fetch 288 rows from an index.
> I'm guessing you have a *lot* of dead rows in there.
Yeah. The other small problem here is that EXPLAIN output hasn't looked
like that since PG 7.2 (unless Soni has just omitted the index-condition
lines). I'd recommend updating to something modern.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2006-04-11 13:49:48 | Re: Stored Procedure Performance |
| Previous Message | Merlin Moncure | 2006-04-11 13:13:24 | Re: Takes too long to fetch the data from database |