From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Sushant Sinha <sushant354(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, Teodor Sigaev <teodor(at)sigaev(dot)ru>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
Subject: | Re: text search: restricting the number of parsed words in headline generation |
Date: | 2012-08-15 16:21:03 |
Message-ID: | 20120815162103.GL25473@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
This might indicate that the hlCover() item is resolved.
---------------------------------------------------------------------------
On Wed, Aug 24, 2011 at 10:08:11AM +0530, Sushant Sinha wrote:
>
>
> Actually, this code seems probably flat-out wrong: won't every
> successful call of hlCover() on a given document return exactly the same
> q value (end position), namely the last token occurrence in the
> document? How is that helpful?
>
> regards, tom lane
>
>
> There is a line that saves the computation state from the previous call and
> search only starts from there:
>
> int pos = *p;
>
>
>
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2012-08-15 16:22:50 | Re: sha1, sha2 functions into core? |
Previous Message | Bruce Momjian | 2012-08-15 16:19:58 | Re: text search: restricting the number of parsed words in headline generation |