Re: pg_index.indislossy - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: pg_index.indislossy
Date
Msg-id 200105150002.f4F02At24143@candle.pha.pa.us
Whole thread Raw
In response to Re: pg_index.indislossy  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> Bruce Momjian <pgman@candle.pha.pa.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@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_index.indislossy
Next
From: Bruce Momjian
Date:
Subject: Re: pg_index.indislossy