From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_index.indislossy |
Date: | 2001-05-15 00:02:10 |
Message-ID: | 200105150002.f4F02At24143@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Should I remove this column?
>
> NO. The fact that we don't currently have any lossy index types doesn't
> mean that we won't ever have them again. I've been wondering, for
> example, whether the frequently heard requests for case-insensitive
> indexes might not be answerable by implementing 'em as lossy indexes.
I see it now. It is just looking for a flag in the index creation:
if (!strcasecmp(param->defname, "islossy"))
That is the extent of the lossy code. There is optimizer code checking
for it. Seems an ifdef NOT_USED around those would document what needs
to be done, and document it doesn't do anything now, or I can just leave
it alone.
--
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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-05-15 00:11:44 | Re: Installation on SGI IRIX 6.5.10 |
Previous Message | G. Anthony Reina | 2001-05-15 00:00:09 | Re: Installation on SGI IRIX 6.5.10 |