> > >As for NULL,it seems possible to look up NULL keys in a btree index
> > >because NULL == NULL for btree indexes.
> > >I've wondered why PostgreSQL's planner/executor never looks up
> > >indexes for queries using 'IS NULL'.
> > Unfortunately for the RI MATCH PARTIAL case, NULL is a "wildcard".
> Oops I misunderstood NULL.
> Hmm,is the following TODO worth the work ?
> * Use index to restrict rows returned by multi-key index when used with
> non-consecutive keys or OR clauses, so fewer heap accesses.
This is a Vadim item.
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2000-04-02 17:06:05|
|Subject: Re: Crash on UPDATE in 7.0beta3 |
|Previous:||From: Bruce Momjian||Date: 2000-04-02 16:36:11|
|Subject: Re: src/test/locale/de_DE.ISO-8859-1|