From: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_index.indislossy |
Date: | 2001-05-15 09:04:14 |
Message-ID: | Pine.GSO.4.33.0105151158510.15894-100000@ra.sai.msu.su |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
GiST certainly use it ! Please don't remove.
GiST uses compression/decompression technique which could
produce false drops.
Oleg
On Mon, 14 May 2001, Bruce Momjian wrote:
> Can someone tell me what we use indislossy for? The only comment I
> could find was:
>
> /*
> * WITH clause reinstated to handle lossy indices. -- JMH, 7/22/96
> */
> foreach(pl, parameterList)
> {
> DefElem *param = (DefElem *) lfirst(pl);
>
> if (!strcasecmp(param->defname, "islossy"))
> lossy = true;
> else
> elog(NOTICE, "Unrecognized index attribute \"%s\" ignored",
> param->defname);
> }
>
> and
>
> bool indislossy; /* do we fetch false tuples (lossy
> * compression)? */
>
> Should I remove this column?
>
>
>
Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83
From | Date | Subject | |
---|---|---|---|
Next Message | Oleg Bartunov | 2001-05-15 09:19:29 | please apply patch for GiST (7.1.1, current cvs) |
Previous Message | Martín Marqués | 2001-05-15 08:26:04 | 7.2 wish list (big change) |