>> comparing the same vectors, but stripped. Oddly, the unstripped comparisons all
>> pass, which is not consistant with what I am seeing in my database. However,
>> I'm yet unable to reproduce those problems.
Fixed: strncmp was called with wrong length parameter.
> It looks to me like tsvector comparison may be too strong. The strip()
> function evidently thinks that it's OK to rearrange the string chunks
> into the same order as the WordEntry items, which suggests to me that
> the "pos" fields are not really semantically significant. But
> silly_cmp_tsvector() considers that a difference in pos values is
> important. I don't understand the data structure well enough to know
> which one to believe, but something's not consistent here.
You are right: Pos really means position of lexeme itself in a tail of tsvector
structure. So, it's removed from comparison.
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
In response to
pgsql-hackers by date
|Next:||From: Chahine Hamila||Date: 2006-08-29 14:19:09|
|Subject: Re: integration of pgcluster into postgresql|
|Previous:||From: Tom Lane||Date: 2006-08-29 13:56:58|
|Subject: Re: [PATCHES] Another VPATH patch for ecpg |