Ivan Sergio Borgonovo <[EMAIL PROTECTED]> writes:
> Tom Lane <[EMAIL PROTECTED]> wrote:
>> I see. So this could explain Ivan's issue if his table contains
>> large numbers of repeated GIN keys. Ivan, is that what your data
>> looks like?
> Well if by GIN keys you mean lexemes it could be. But I wouldn't say
> this circumstance is uncommon among users of tsearch. I'd expect
> other people had used tsearch2 to search through titles, authors and
> publishers of books, so if that was the problem I'd expect the
> problem to come up earlier.
Yeah, I'm not convinced either. Still, Teodor's theory should be easily
testable: set synchronize_seqscans to FALSE and see if the problem goes
away.
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
