Re: Index question - Mailing list pgsql-sql

From David Witham
Subject Re: Index question
Date
Msg-id CFA248776934FD43847E740E43C346D199DBF0@ozimelb03.ozicom.com
Whole thread Raw
In response to Index question  ("David Witham" <davidw@unidial.com.au>)
List pgsql-sql
There are 18321 records for 20040127 and so the estimate of 8839 for the = case is low but it still does the right
thing.

There are 227197 records between '20040127' and current_date so the estimate in the >= case is accurate but the
estimatefor the between case is an order of magnitude too low. However, it used the index I wanted and the >= case
didn't.

Regards,
David

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Friday, 13 February 2004 16:38
To: David Witham
Cc: pgsql-sql@postgresql.org
Subject: Re: [SQL] Index question


"David Witham" <davidw@unidial.com.au> writes:
> I understand that selecting count(*) will involve a scan at some
> stage, but I was surprised that the index wasn't used in the >= case,
> but was used in the between case.

Given the estimated row counts in your examples, the planner's choices
are not surprising.  You have not given us any information on whether
those estimates are accurate.
        regards, tom lane


pgsql-sql by date:

Previous
From: "Kumar"
Date:
Subject: Re: How to avoid nulls while writing string for dynamic query
Next
From: Tomasz Myrta
Date:
Subject: Re: How to avoid nulls while writing string for dynamic query