| From: | "Harmon S(dot) Nine" <hnine(at)netarx(dot)com> |
|---|---|
| To: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Timestamp-based indexing |
| Date: | 2004-07-26 18:37:48 |
| Message-ID: | 41054F7C.3020108@netarx.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
THAT WAS IT!!
Thank you very much.
Is there a way to change the type of "CURRENT_TIMESTAMP" to "timestamp
without time zone" so that casting isn't needed?
BTW, isn't this a bug?
-- Harmon
Stephan Szabo wrote:
>On Mon, 26 Jul 2004, Harmon S. Nine wrote:
>
>
>
>>However, we can't get the planner to do an timestamp-based index scan.
>>
>>Anyone know what to do?
>>
>>
>
>I'd wonder if the type conversion is causing you problems.
>CURRENT_TIMESTAMP - INTERVAL '10 minutes' is a timestamp with time zone
>while the column is timestamp without time zone. Casting
>CURRENT_TIMESTAMP to timestamp without time zone seemed to make it able to
>choose an index scan on 7.4.
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ross J. Reedstrom | 2004-07-26 18:47:03 | Re: arrays and indexes |
| Previous Message | Scott Marlowe | 2004-07-26 16:25:38 | Re: Insert are going slower ... |