AW: pg_index.indislossy - Mailing list pgsql-hackers

From Zeugswetter Andreas SB
Subject AW: pg_index.indislossy
Date
Msg-id 11C1E6749A55D411A9670001FA6879633682C6@sdexcsrv1.f000.d0188.sd.spardat.at
Whole thread Raw
List pgsql-hackers
> > 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


pgsql-hackers by date:

Previous
From: Oleg Bartunov
Date:
Subject: please apply patch for GiST (7.1.1, current cvs)
Next
From: Zeugswetter Andreas SB
Date:
Subject: AW: pg_index.indislossy