From: | markw(at)osdl(dot)org |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
Cc: | josh(at)agliodbs(dot)com, pgsql-hackers(at)postgresql(dot)org, jenny(at)osdl(dot)org |
Subject: | Re: Proposed Query Planner TODO items |
Date: | 2004-02-16 17:18:11 |
Message-ID: | 200402161718.i1GHIpE05481@mail.osdl.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 15 Feb, Tom Lane wrote:
> I wrote:
>> I see what is going on to make Q4 slow, too. It's this:
>> where o_orderdate >= date '1995-04-01' and o_orderdate < date '1995-04-01' + interval '3 month'
>> ...
>> As of CVS tip the issue could be eliminated by introducing
>> cross-data-type comparison operators between types date and timestamp
>> without time zone, and then making these be members of the date index
>> opclass. I'm strongly tempted to do so ...
>
> I have now done this, so if you care to re-sync with CVS tip you should
> find that the queries using this sort of date constraint go faster.
> (You do have indexes on all the date columns, no?)
I ran a test with the CAST you recommended for Q4 over the weekend:
http://developer.osdl.org/markw/dbt3-pgsql/68/
But it didn't seem to have much of an affect on Q4, compared to run
#66. I'll still give the CVS tip a try.
Mark
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-02-16 17:58:00 | Re: Proposed Query Planner TODO items |
Previous Message | Rod Taylor | 2004-02-16 16:54:44 | Slow DROP INDEX |