Re: Problem with large table not using indexes (I think) - Mailing list pgsql-general

From Benjamin Arai
Subject Re: Problem with large table not using indexes (I think)
Date
Msg-id 458D88C8.8010702@benjaminarai.com
Whole thread Raw
In response to Re: Problem with large table not using indexes (I think)  (Benjamin Arai <benjamin@araisoft.com>)
List pgsql-general
One more note about my problem,  when you run a query on older data in
the table then it work great but if you query newer data then is very slow.

Ex.

SELECT * from my_table WHERE date >=12/1/2005 and date <= 12/1/2006; <- slow

SELECT * from my_table WHERE date >=12/1/2002 and date <= 12/1/2003; <- fast

It just has to do with the new data for some reason.

Benjamin


Benjamin Arai wrote:
> Function Scan on "getTimeSeries"  (cost=0.00..12.50 rows=1000
> width=24) (actual time=11065.981..11067.008 rows=262 loops=1)
> Total runtime: 11067.991 ms
> (2 rows)
>
> It is a PL function.  Do I need to break it down?
>
> A. Kretschmer wrote:
>> am  Sat, dem 23.12.2006, um 11:26:08 -0800 mailte Benjamin Arai
>> folgendes:
>>
>>> because it would literally take over a week to complete.  Any help
>>> would be greatly appreciated.
>>>
>>
>> What says an 'explain analyse'?
>>
>>
>> Andreas
>>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>

pgsql-general by date:

Previous
From: "Stuart Grimshaw"
Date:
Subject: ERROR: could not access status of transaction
Next
From: "Shoaib Mir"
Date:
Subject: Re: psql "SCHEMA" switch