From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Hannu Krosing <hannu(at)tm(dot)ee>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_index.indislossy |
Date: | 2001-05-14 21:33:02 |
Message-ID: | Pine.BSF.4.33.0105141832310.68237-100000@mobile.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 14 May 2001, Bruce Momjian wrote:
> > Bruce Momjian wrote:
> > >
> > > Can someone tell me what we use indislossy for?
> >
> > IIRC it means that if you get something by this index you must check
> > again in the actual data
> >
> > I think that at least the GIST intarray (actually intset) methods use
> > it.
> >
> > So you probably should _not_ remove it ;)
>
> I did a search and found it used only a few places. I do not see it
> used as part of GIST. My rememberance is that it is involved in partial
> indexes, where you index only certain values in a column. It was an old
> idea that was never working in PostgreSQL.
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
...
From | Date | Subject | |
---|---|---|---|
Next Message | Marko Kreen | 2001-05-14 21:47:13 | Re: Re: bug in pgcrypto 0.3 |
Previous Message | Peter Eisentraut | 2001-05-14 21:09:40 | Re: 7.2 items |