Re: BETWEEN optimizer problems with single-value

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Tom Lane <tgl@xxxxxxxxxxxxx>
Subject: Re: BETWEEN optimizer problems with single-value
From: Simon Riggs <simon@xxxxxxxxxxxxxxx>
Date: Thu, 16 Mar 2006 00:07:06 +0000
Cc: Kevin Grittner <Kevin.Grittner@xxxxxxxxxxxx>, pgsql-performance@xxxxxxxxxxxxxx, Andreas Kretschmer <akretschmer@xxxxxxxxxxxxx>
In-reply-to: <28798.1142450270@xxxxxxxxxxxxx>
References: <44180105.EE98.0025.0@xxxxxxxxxxxx> <20060315181735.GA22240@KanotixBox> <44180D33.EE98.0025.0@xxxxxxxxxxxx> <28798.1142450270@xxxxxxxxxxxxx>

On Wed, 2006-03-15 at 14:17 -0500, Tom Lane wrote:

> It looks to me like this is a matter of bad cost estimation, ie, it's
> thinking the other index is cheaper to use.  Why that is is not clear.
> Can we see the pg_stats rows for ctofcNo and calDate?

ISTM that when the BETWEEN constants match we end up in this part of
clauselist_selectivity()...

Follow-Ups:
- Re: BETWEEN optimizer problems with single-value
  - From: Simon Riggs

References:
- BETWEEN optimizer problems with single-value range
  - From: Kevin Grittner
- Re: BETWEEN optimizer problems with single-value range
  - From: Andreas Kretschmer
- Re: BETWEEN optimizer problems with single-value
  - From: Kevin Grittner
- Re: BETWEEN optimizer problems with single-value
  - From: Tom Lane

Prev by Date: Re: [HACKERS] BETWEEN optimizer problems with single-value
Next by Date: Re: BETWEEN optimizer problems with single-value
Previous by thread: Re: BETWEEN optimizer problems with single-value
Next by thread: Re: BETWEEN optimizer problems with single-value
Index(es):
- Date
- Thread

[Postgresql General] [Postgresql PHP] [PHP Users] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Yosemite]

Powered by Linux