As an update, I've just copied the tsvector.dll file from an 8.2.1 computer
to the 8.2.3 computer and it's working OK now. I suspect a change in the dll
is causing the problem.
Richard
richardcraig wrote:
>
> Oleg
>
> Thanks for the quick response.
>
> On 8.2.1 I get the same result as yourself, however on 8.2.3 I get
> (2,"test text")
>
> Configuration?
> Both databases are UTF8 encoded with language set to C
> Standard windows installation except for tsearch2
> I also have another machine with SQL_ASCII encoding on 8.2.1 and that's OK
>
> As far as I can tell they are identical except for the postgresql
> versions.
>
> It's been a long time since I did much with tsearch2 so I'm suspecting a
> config problem with it that's I've long forgotten about.
>
> Richard
>
>
> Oleg Bartunov wrote:
>>
>> What parse returns ? 8.1.5 and 8.3 return
>>
>> www=# select parse('test text');
>> parse
>> ----------
>> (1,test)
>> (12," ")
>> (1,text)
>> (3 rows)
>>
>> Also, what is your configuration ?
>>
>>
>> On Wed, 21 Mar 2007, richardcraig wrote:
>>
>>>
>>> It may solve my query if anybody can tell me if anything has changes in
>>> tsearch2 recently? otherwise...
>>>
>>> I have two installations of Postgres on Windows machines, one is 8.2.1
>>> and
>>> the other is 8.2.3
>>>
>>> Both installed the same way, selecting tsearch2 during the installation
>>> and
>>> restoring the same backup database file.
>>>
>>> In 8.2.1
>>> select to_tsvector('test text')
>>> returns
>>> 'test':1 'text':2
>>> as expected
>>>
>>> In 8.2.3 the same code returns
>>> 'test text':1
>>>
>>> Can anybody help?
>>>
>>
>> Regards,
>> Oleg
>> _____________________________________________________________
>> Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru),
>> Sternberg Astronomical Institute, Moscow University, Russia
>> Internet: oleg@xxxxxxxxxx, http://www.sai.msu.su/~megera/
>> phone: +007(495)939-16-83, +007(495)939-23-83
>>
>> ---------------------------(end of broadcast)---------------------------
>> TIP 9: In versions below 8.0, the planner will ignore your desire to
>> choose an index scan if your joining column's datatypes do not
>> match
>>
>>
>
>
--
View this message in context: http://www.nabble.com/to_tsvector-in-8.2.3-tf3440132.html#a9592812
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
