From: | Benjamin Arai <me(at)benjaminarai(dot)com> |
---|---|
To: | Benjamin Arai <benjamin(at)araisoft(dot)com> |
Cc: | "A(dot) Kretschmer" <andreas(dot)kretschmer(at)schollglas(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Problem with large table not using indexes (I think) |
Date: | 2006-12-23 19:51:36 |
Message-ID: | 458D88C8.8010702@benjaminarai.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin 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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Benjamin Arai | 2006-12-23 19:52:06 | Re: Problem with large table not using indexes (I think) |
Previous Message | Benjamin Arai | 2006-12-23 19:48:56 | Re: Problem with large table not using indexes (I think) |
From | Date | Subject | |
---|---|---|---|
Next Message | Benjamin Arai | 2006-12-23 19:52:06 | Re: Problem with large table not using indexes (I think) |
Previous Message | Benjamin Arai | 2006-12-23 19:48:56 | Re: Problem with large table not using indexes (I think) |