Re: AW: pg_index.indislossy - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: AW: pg_index.indislossy
Date
Msg-id Pine.LNX.4.30.0107101651370.677-100000@peter.localdomain
Whole thread Raw
In response to Re: AW: pg_index.indislossy  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: AW: pg_index.indislossy
Re: AW: pg_index.indislossy
List pgsql-hackers
Bruce Momjian writes:

> > > > > Can someone tell me what we use indislossy for?
> >
> > Ok, so the interpretation of this field is:
> >     A match in the index needs to be reevaluated in the heap tuple data,
> >     since a match in the index does not necessarily mean, that the heap tuple
> >     matches.
> >     If the heap tuple data matches, the index must always match.

AFAIK, this is true for all indexes in PostgreSQL, because index rows
don't store the transactions status.  Of course those are two different
underlying reasons why a heap lookup is always necessary, but there
shouldn't be any functional difference in the current implementation.

-- 
Peter Eisentraut   peter_e@gmx.net   http://funkturm.homeip.net/~peter



pgsql-hackers by date:

Previous
From: Jan Wieck
Date:
Subject: Re: Any tips for this particular performance problem?
Next
From: Zeugswetter Andreas SB
Date:
Subject: AW: AW: pg_index.indislossy