Re: [GENERAL] Fragments in tsearch2 headline

> A couple of caveats:
>
> 1. ts_headline testing was done with current cvs head where as
> headline_with_fragments was done with postgres 8.3.1.
> 2. For headline_with_fragments, TSVector for the document was obtained
> by joining with another table.
> Are these differences understandable?

That is possible situation because ts_headline has several criterias of 'best'
covers - length, number of words from query, good words at the begin and at the
end of headline while your fragment's algorithm takes care only on total number
of words in all covers. It's not very good, but it's acceptable, I think.
Headline (and ranking too) hasn't any formal rules to define is it good or bad?
Just a people's opinions.

Next possible reason: original algorithm had a look on all covers trying to find
the best one while your algorithm tries to find just the shortest covers to fill
a headline.

But it's very desirable to use ShortWord - it's not very comfortable for user if
one option produces unobvious side effect with another one.
`

> If you think these caveats are the reasons or there is something I am
> missing, then I can repeat the entire experiments with exactly the same
> conditions.

Interesting for me test is a comparing hlCover with Cover in your patch, i.e.
develop a patch which uses hlCover instead of Cover and compare old patch with
new one.
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/