On Tue, 20 Nov 2001, Bruce Momjian wrote:
> So, while we do have plans to mark some index tuples so we _know_ they
> are expired, we don't know how to efficiently mark index tuples so we
> _know_ they are valid.
>
> This is what I believe you want, where we can scan the index without
> checking the heap at all.
An new index type (say READONLY INDEX or some reasonable name) which is
valid all the time between two vacuum processes would suffice for my
application. It would fit the needs of people who do a daily database
update and vacuum after this.
Of course it´s your descision if this makes sense and fits PostgreSQL
philosophy, but I think it would speed up some kind of applications.
Kind regards
Andreas.
