Re: Incorrect FTS result with GIN index

Artur,

you could get much more problems in future. Full text search problem may be
signature of more general problem with your postgres setup. So, I'd recommend
to find a source of the problem

Oleg
On Tue, 20 Jul 2010, Artur Dabrowski wrote:

>
> Oleg,
>
> thanks for your help.
>
> I sent a post to pg-hackers list:
> http://old.nabble.com/Query-results-differ-depending-on-operating-system-%28using-GIN%29-ts29213082.html
>
> As to compiling pg... I will no do this since I do not really feel
> comfortable doing it and cannot dedicate too much time to this problem.
>
> Artur
>
>
>
> Oleg Bartunov wrote:
>>
>> Artur,
>>
>> I recommend post your problem to -hackers mailing list. I have no idea,
>> what could be a problem.
>>
>> My machine is:
>> uname -a
>> Linux mira 2.6.33-020633-generic #020633 SMP Thu Feb 25 10:10:03 UTC 2010
>> x86_64 GNU/Linux
>>
>> PostgreSQL 8.4.4 on x86_64-unknown-linux-gnu, compiled by GCC gcc (Ubuntu
>> 4.4.1-4ubuntu9) 4.4.1, 64-bit
>>
>> As a last resort I recommend you to compile pg yourself and see if the
>> problem exists.
>>
>> Oleg
>>
>>
>> On Tue, 20 Jul 2010, Artur Dabrowski wrote:
>>
>>>
>>> I tested the same backup on our CentOS 5.4 virtual machine (running on
>>> xen
>>> server) and the results are really weird (118 rows, comparing to 116 on
>>> win
>>> xp and 123 expected):
>>>
>>> Aggregate (cost=104.00..104.01 rows=1 width=0) (actual
>>> time=120.373..120.374 rows=1 loops=1)
>>> -> Bitmap Heap Scan on search_tab (cost=5.35..103.93 rows=25 width=0)
>>> (actual time=59.418..120.137 rows=118 loops=1)
>>> Recheck Cond: ((to_tsvector('german'::regconfig, keywords) @@
>>> '''ee'':*'::tsquery) AND (to_tsvector('german'::regconfig, keywords) @@
>>> '''dd'':*'::tsquery))
>>> -> Bitmap Index Scan on idx_keywords_ger (cost=0.00..5.34
>>> rows=25
>>> width=0) (actual time=59.229..59.229 rows=495 loops=1)
>>> Index Cond: ((to_tsvector('german'::regconfig, keywords) @@
>>> '''ee'':*'::tsquery) AND (to_tsvector('german'::regconfig, keywords) @@
>>> '''dd'':*'::tsquery))
>>> Total runtime: 120.670 ms
>>>
>>> And here are the configuration details:
>>>
>>> PostgreSQL:
>>> postgresql84-server-8.4.4-1.el5_5.1
>>>
>>> # uname -r
>>> 2.6.18-164.15.1.el5xen
>>>
>>> # cat /etc/redhat-release
>>> CentOS release 5.4 (Final)
>>>
>>> # cat /proc/cpuinfo
>>> processor : 0
>>> vendor_id : GenuineIntel
>>> cpu family : 6
>>> model : 15
>>> model name : Intel(R) Xeon(R) CPU 5140 @ 2.33GHz
>>> stepping : 6
>>> cpu MHz : 2333.416
>>> cache size : 4096 KB
>>> physical id : 0
>>> siblings : 1
>>> core id : 0
>>> cpu cores : 1
>>> fpu : yes
>>> fpu_exception : yes
>>> cpuid level : 10
>>> wp : yes
>>> flags : fpu de tsc msr pae cx8 apic sep cmov pat clflush acpi
>>> mmx
>>> fxsr sse sse2 ss ht syscall lm constant_tsc pni cx16 lahf_lm
>>> bogomips : 5835.83
>>> clflush size : 64
>>> cache_alignment : 64
>>> address sizes : 36 bits physical, 48 bits virtual
>>> power management:
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Oleg Bartunov wrote:
>>>>
>>>> Artur,
>>>>
>>>> I don't know, but could you try linux machine ?
>>>>
>>>> Oleg
>>>>
>>>
>>>
>>
>> Regards,
>> Oleg
>> _____________________________________________________________
>> Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru),
>> Sternberg Astronomical Institute, Moscow University, Russia
>> Internet: oleg(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
>> phone: +007(495)939-16-83, +007(495)939-23-83
>>
>> --
>> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-general
>>
>>
>
>

Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru),
Sternberg Astronomical Institute, Moscow University, Russia
Internet: oleg(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
phone: +007(495)939-16-83, +007(495)939-23-83