| From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
|---|---|
| To: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
| Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Indexam interface proposal |
| Date: | 2007-03-19 14:27:58 |
| Message-ID: | 45FE9DEE.5090600@sigaev.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Interesting. So we'd add a flag to the index tuples in GiST indicating
> if the tuple is lossily compressed or not. The compress-function would
> set that flag when it performs lossy compression, and gistgettuple would
> return it to the caller.
Keys in GiST index may be another type than column on which index was created,
so gistgettuple can not return tuple in original form - but sometimes
gistgettuple may be sure that recheck isn't needed.
> That would completely replace the current RECHECK-option we have, right?
Yeah, this is possible.
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2007-03-19 14:34:28 | Back from vacation |
| Previous Message | Hannu Krosing | 2007-03-19 14:26:21 | Re: CREATE INDEX and HOT (was Question: pg_classattributes and race conditions ?) |