AW: GiST index on data types that require compression

From: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
To: "'Teodor Sigaev'" <teodor(at)stack(dot)net>, 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: AW: GiST index on data types that require compression
Date: 2001-05-28 06:59:48
Message-ID: 11C1E6749A55D411A9670001FA6879633682F4@sdexcsrv1.f000.d0188.sd.spardat.at
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

Those are both properties of the compress function, the index method or the key type.
I do not think it has anything to do with operator classes (comparison functions),
and thus would be wrong in pg_opclass.

Andreas

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas SB 2001-05-28 08:02:17 AW: Plans for solving the VACUUM problem
Previous Message Joe Conway 2001-05-28 05:02:17 remote database queries