Re: GiST index on data types that require compression

From: Teodor Sigaev <teodor(at)stack(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Dave Blasby <dblasby(at)refractions(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: GiST index on data types that require compression
Date: 2001-05-25 14:42:58
Message-ID: 3B0E6F72.4090209@stack.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)stack(dot)net

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Teodor Sigaev 2001-05-25 16:29:21 Re: GiST index on data types that require compression
Previous Message Tom Lane 2001-05-25 14:26:11 Re: PQsetdbLogin bug?