Re: AW: pg_index.indislossy

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: AW: pg_index.indislossy
Date: 2001-07-10 14:56:01
Message-ID: 200107101456.f6AEu1A07420@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

Seems it is something they added for the index abstraction and not for
practical use by PostgreSQL.

--
Bruce Momjian | http://candle.pha.pa.us
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

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas SB 2001-07-10 15:06:12 AW: AW: pg_index.indislossy
Previous Message Jan Wieck 2001-07-10 14:54:54 Re: Any tips for this particular performance problem?