Re: Index question

Поиск
Список
Период
Сортировка
От David Witham
Тема Re: Index question
Дата
Msg-id CFA248776934FD43847E740E43C346D199DBF0@ozimelb03.ozicom.com
обсуждение исходный текст
Ответ на Index question  ("David Witham" <davidw@unidial.com.au>)
Список 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 по дате отправления:

Предыдущее
От: "Kumar"
Дата:
Сообщение: Re: How to avoid nulls while writing string for dynamic query
Следующее
От: Tomasz Myrta
Дата:
Сообщение: Re: How to avoid nulls while writing string for dynamic query