Re: Incorrect FTS result with GIN index

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
Cc: Artur Dabrowski <ad(at)astec(dot)com(dot)pl>, pgsql-general(at)postgresql(dot)org
Subject: Re: Incorrect FTS result with GIN index
Date: 2010-07-28 00:27:48
Message-ID: 19427.1280276868@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> writes:
> I recommend post your problem to -hackers mailing list. I have no idea,
> what could be a problem.

I wonder whether the problem is not windows versus non windows but
original database versus copies. If it is a GIN bug it seems quite
possible that it would depend on the order of insertion of the index
entries, which a simple dump-and-reload probably wouldn't duplicate.

If you were working from a dump it'd be easy to try creating the index
before populating the table to see if the bug can be reproduced then,
but there's no certainty that would provoke the bug.

The rest of us have not seen the dump data, so we have no hope of
doing anything with this report anyway.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message raf 2010-07-28 00:46:31 postgres-8.4SS, pg_dump from macosx-10.6 has "ssl handshake error" 26% in
Previous Message Dann Corbit 2010-07-27 23:12:13 Re: Histogram generator

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2010-07-28 02:55:18 Re: Toward a column reorder solution
Previous Message Jeff Davis 2010-07-27 23:55:52 Re: Review: Re: [PATCH] Re: [HACKERS] Adding xpath_exists function