| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: knngist - 0.8 |
| Date: | 2010-12-04 18:25:21 |
| Message-ID: | AANLkTin_qT_ShY-=dJwxhFHFoZjm_MwsChGKw4MD5acA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Dec 4, 2010 at 6:07 PM, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> wrote:
> We'll sync contrib/btree_gist with current API. Also, we're thinking
> about distance for ltree, boxes, circles. I'm not sure about polygons,
> though.
> So, we'll have rather complete set of knn-fied data types.
I kind of assumed the natural client for KNN-gist was the tsearch full
text search indexes handling sorting by relevance. For example if I
search for "Postgres DBA" I should find documents where those words
appear adjacent first and documents where the two words appear far
apart in the document sorted further down. Is that not on the list of
operators supported or planned to be supported?
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2010-12-04 18:56:35 | Re: FK's to refer to rows in inheritance child |
| Previous Message | Dimitri Fontaine | 2010-12-04 18:22:42 | Re: FK's to refer to rows in inheritance child |