> > > * Prevent index lookups (or index entries using partial index) on most
> > > common values; instead use sequential scan
> >
> > This behavior already exists for the most common value, and would
> > exist for any additional values that we had stats for. Don't see
> > why you think a separate TODO item is needed.
>
> You mean the optimizer already skips an index lookup for the most common
> value, and instead does a sequential scan? Seems you are way ahead of
> me.
If the answer is yes, how do you prevent a join that hits the most
common value?
--
Bruce Momjian | http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
