BUG #3975: tsearch2 index should not bomb out of 1Mb limit

From: "Edwin Groothuis" <postgresql(at)mavetju(dot)org>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #3975: tsearch2 index should not bomb out of 1Mb limit
Date: 2008-02-21 07:16:53
Message-ID: 200802210716.m1L7GrGi064774@wwwmaster.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-patches


The following bug has been logged online:

Bug reference: 3975
Logged by: Edwin Groothuis
Email address: postgresql(at)mavetju(dot)org
PostgreSQL version: 8.3
Operating system: FreeBSD 6.3
Description: tsearch2 index should not bomb out of 1Mb limit
Details:

I have been experimenting with indexing the FreeBSD mailinglist into a
tsearch2 powered/backended database.

Sometimes I see these warning:

NOTICE: word is too long to be indexed
DETAIL: Words longer than 2047 characters are ignored.

That's okay, I can live with that. However, I see this one too:

ERROR: string is too long for tsvector

Ouch. But... since very long words are already not indexed (is the length
configurable anywhere because I don't mind setting it to 50 characters), I
don't think that it should bomb out of this but print a similar warning like
"String only partly indexed".

I'm still trying to determine how big the message it failed on was...

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Gregory Stark 2008-02-21 11:07:58 Re: BUG #3965: UNIQUE constraint fails on long column values
Previous Message Markus Bertheau 2008-02-21 02:01:39 Incomplete docs for restore_command for hot standby

Browse pgsql-patches by date

  From Date Subject
Next Message Richard Huxton 2008-02-21 08:49:37 Re: ts_headline
Previous Message Markus Bertheau 2008-02-21 02:01:39 Incomplete docs for restore_command for hot standby