Re: Index usage on date feild , differences in '>' and '>='

From: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
To: "Rajesh Kumar Mallah(dot)" <mallah(at)trade-india(dot)com>
Cc: <pgsql-sql(at)postgresql(dot)org>
Subject: Re: Index usage on date feild , differences in '>' and '>='
Date: 2002-09-19 06:37:39
Message-ID: 20020918233621.A23870-100000@megazone23.bigpanda.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

On Thu, 19 Sep 2002, Rajesh Kumar Mallah. wrote:

> I am trying to improve a query to use existing indexes but facing diffculty.
>
>
> Looks like 'between' amd '>=' are not using indexes althoug > and < does.
> all my application code uses between and i am sure it use to work fine
> at one point of time.
>
>
> regds
> mallah.
>
> SQL TRANSCRIPT:
> ======================================================================================
>
> tradein_clients=> explain select list_id from eyp_rfi a where generated > '2002-08-13' and generated < '2002-09-19' ;
> NOTICE: QUERY PLAN:
>
> Index Scan using eyp_rfi_date on eyp_rfi a (cost=0.00..15796.97 rows=4150 width=4)
>
> EXPLAIN
> tradein_clients=> explain select list_id from eyp_rfi a where generated >= '2002-08-13' and generated < '2002-09-19' ;
> NOTICE: QUERY PLAN:
>
> Seq Scan on eyp_rfi a (cost=0.00..17923.81 rows=5061 width=4)

Given how close the two results are (and the fact that they differ by 900
rows), have you tried using set enable_seqscan=off and seeing what
explain gives you for the second query? My guess is that it'll have
an estimated cost greater than the 17923.81 it's estimating from the
sequence scan.

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Rajesh Kumar Mallah. 2002-09-19 06:38:46 Index usage on date feild , differences in '>' and '>=' and between
Previous Message Stephan Szabo 2002-09-18 21:58:56 Re: Performance w/ multiple WHERE clauses