From: | Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com> |
---|---|
To: | Rafael Domiciano <rafael(dot)domiciano(at)gmail(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: SQL With Dates |
Date: | 2009-04-20 14:14:15 |
Message-ID: | 2f4958ff0904200714x2beda1d2pa0136080e84d15e0@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
BETWEEN X AND Y
On Mon, Apr 20, 2009 at 2:55 PM, Rafael Domiciano
<rafael(dot)domiciano(at)gmail(dot)com> wrote:
> Hello People,
>
> I have initiated a work to review the sqls of our internal software.
> Lot of them he problem are about sql logic, or join with table unecessary,
> and so on.
> But software has lot of sql with date, doing thinks like:
> [..]
> date >= '2009-04-01' AND
> date <= '2009-04-15'
> [..]
>
> Redoing the SQL with fix date (date = '2009-04-01') o cost in explain always
> still about 200 or less. But with a period the cost is high, about 6000 or
> more.
>
> Select is using Index and the date is using index too.
>
> There is some way to use date period with less cost?
>
> Rafael Domiciano
>
--
GJ
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-04-20 15:27:00 | Re: GiST index performance |
Previous Message | Matthew Wakeling | 2009-04-20 14:11:08 | Re: GiST index performance |