> > > * 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
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

Sun, 15 Oct 2000 17:55:22 -0400 (EDT)
Bruce Momjian <pgman@candle.pha.pa.us>
Re: Performance on inserts