Re: GiST index on data types that require compression

From: Teodor Sigaev <teodor(at)stack(dot)net>
To: Teodor Sigaev <teodor(at)stack(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 16:29:21
Message-ID: 3B0E8861.5040508@stack.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

Sorry, I was wrong. In GiST, index_formtuple doesn't know about size of
fixed-length type of keys, because only loadable module has information
about structure of key. So, may be it needs to have function which
return size of key or index_formtuple must looks at GISTENTRY.bytes(
Note: A lot of currrent implementation of GiST modules don't set value
GISTENTRY.bytes ). Or fields in pg_opclass:
int len_key
bool is_lossy_compress

if len_key==-1 then key is varlena type.

--
Teodor Sigaev
teodor(at)stack(dot)net

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mikheev, Vadim 2001-05-25 16:37:16 RE: Plans for solving the VACUUM problem
Previous Message Teodor Sigaev 2001-05-25 14:42:58 Re: GiST index on data types that require compression