| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
| Cc: | cluster <skrald(at)amossen(dot)dk>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: tsearch2: plainto_tsquery() with OR? |
| Date: | 2007-08-09 06:40:07 |
| Message-ID: | 4628.1186641607@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> writes:
> On Thu, 9 Aug 2007, Tom Lane wrote:
>> ... behavior that people want is "here's some words, get me a weighted
>> result", and if the weighting improves from time to time that's OK.
>> We need to provide that API too.
> I think I understand. It's called non-exact (approximate) matching,
Right, exactly. I don't claim that we have a perfect solution for
approximate matching; we don't. But I think we should provide an
API function that is defined to do approximate matching, with the
understanding that the details of its behavior will change (for the
better hopefully) from release to release. The first version might
not be very good, but we can improve it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Trevor Talbot | 2007-08-09 06:47:03 | Re: tsearch2: plainto_tsquery() with OR? |
| Previous Message | Oleg Bartunov | 2007-08-09 06:30:37 | Re: tsearch2: plainto_tsquery() with OR? |