
> > Let's avoid removing things for the sake of removing them ... might be an
> > old idea that, if someone takes the time to research, might prove useful
> > ...
> 
> Yea, there is actually some code attached to this vs. the others that
> had no code at all.  Are we ever going to do partial indexes?  I guess
> that is the question.

The idea is very very good, and since there is an exaple implementation in 
pg 4 it should probably be possible to reimplement. (DB2 has this feature also)

In real life, you would e.g. index a status column for rows, that need more work.
create index deposit_status_index on deposit (status) where status <> 0;
99% of your rows would have status = 0 thus the index would be extremely 
efficient for all select statements that search for a specific status other than 0.  

Imho it would be a shame to give up that idea so easily.

Andreas

Tue, 15 May 2001 12:07:32 +0200
Zeugswetter Andreas SB  <ZeugswetterA@wien.spardat.at>
AW: pg_index.indislossy
> > Yea, there is actually some code attached to this vs. the others that
> > had no code at all.  Are we ever going to do partial indexes?  I guess
> > that is the question.
> The idea is very very good, and since there is an exaple implementation in
> pg 4 it should probably be possible to reimplement. (DB2 has this feature also)
...
> Imho it would be a shame to give up that idea so easily.

Agreed. Another common example is to create an index on all non-null
values of a column.

                    - Thomas

Tue, 15 May 2001 12:40:51 +0000
Thomas Lockhart <lockhart@alumni.caltech.edu>
Re: AW: pg_index.indislossy