From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
Subject: | Re: knngist - 0.8 |
Date: | 2010-12-23 03:05:33 |
Message-ID: | AANLkTikFwwb_Dp1t9s1r5Hp-nr5HDYgfkeb3wpwp6ULG@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Dec 22, 2010 at 8:04 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Tom Lane wrote:
>> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> > 2010/9/13 Teodor Sigaev <teodor(at)sigaev(dot)ru>:
>> >> [updated patch]
>>
>> > I realize I'm repeating myself, but... this patch needs
>> > documentation. It's not optional.
>>
>> I've applied all of this, and written documentation for all of it,
>> except for the contrib/btree_gist additions which still need to be
>> redone for the revised API (and then documented!). My patience ran out
>> somewhere around there, so I'm marking that part as returned with
>> feedback.
>>
>> What we have at this point (pending contrib/btree_gist fixes) is
>> nearest-neighbor searching capability for point columns. And
>> trigram-based nearest-neighbor for text strings, if you install
>> contrib/pg_trgm. That doesn't seem like a lot of return for the
>> amount of work that went into it. Are there plans to add KNN support
>> for any other standard types?
>
> I was thinking /contrib/fuzzystrmatch could use it to find the words
> that mostly closely match a string.
Seems unlikely to be feasible.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Sushant Sinha | 2010-12-23 05:35:30 | Re: english parser in text search: support for multiple words in the same position |
Previous Message | Jan Urbański | 2010-12-23 02:08:04 | Re: pl/python improvements |