From: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
---|---|
To: | James Croft <noemail(at)address(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: tsearch2 problems / limitations |
Date: | 2005-02-23 08:01:01 |
Message-ID: | Pine.GSO.4.62.0502231058180.28080@ra.sai.msu.su |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, 22 Feb 2005, James Croft wrote:
> Hi,
>
> I've successfully added tsearch2 to an existing database and the speedup of
> searches is brilliant. I'm now trying to extend this to other parts of our
> system.
>
> One of the tables holds reasonable amounts of text, some fields hold up to
> 2Mb. When I try and run
>
> UPDATE table SET idxfti=to_tsvector('default', field);
>
> it runs for a while then aborts with the following message
>
> ERROR: value is too big
>
> Does anyone know what the problem might be here? Does tsearch2 have
> configurable (or compilable) settings that could get around this?
this is tsearch2 limitation on length of ts_vector about 1mb.
you may stop using postional information for this vector.
>
> Many Thanks,
> James
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2005-02-23 08:12:40 | Re: Different execution time from psql and JDBC |
Previous Message | Manfred Koizar | 2005-02-23 07:18:02 | Re: Does indexing help >= as well as = for integer columns? |