| From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Indexam interface proposal |
| Date: | 2007-03-19 14:36:23 |
| Message-ID: | 45FE9FE7.8090807@sigaev.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Given that rechecking requires Expr and state structures, maybe it would
> be easier to make the operators RECHECK so the planner does the right
> thing now, but make a flag that tells the index scan *not* to recheck
> this tuple. That would seem slightly less work and fit better with the
> existing code. (In other words, it's an optimisation rather than a big
> change).
I like your suggestion - it's useful for GiST/GIN fulltext indexing.
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2007-03-19 14:49:49 | Re: CREATE INDEX and HOT (was Question:pg_classattributes and race conditions ?) |
| Previous Message | Bruce Momjian | 2007-03-19 14:34:28 | Back from vacation |