Re: GiST index on data types that require compression - Mailing list pgsql-hackers

From Teodor Sigaev
Subject Re: GiST index on data types that require compression
Date
Msg-id 3B0E6F72.4090209@stack.net
Whole thread Raw
In response to Re: GiST index on data types that require compression  (Oleg Bartunov <oleg@sai.msu.su>)
Responses Re: GiST index on data types that require compression
List pgsql-hackers
> What I find just about as objectionable as the old haskeytype hack is
> that the user has to tell you whether the index is lossy or not.  This
> should be a property available from the system catalogs.  Not sure where
> to put it; do we need another column in pg_opclass, or is someplace
> other than the opclass needed?
> 

So, may by add to pg_opclass two fields?
bool is_varlena_key
bool is_lossy_compress

Then index_formtuple must look at is_varlena_key and 'with (islossy)' 
could be determined automatically by view at used ops.



-- 
Teodor Sigaev
teodor@stack.net




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: PQsetdbLogin bug?
Next
From: Teodor Sigaev
Date:
Subject: Re: GiST index on data types that require compression