mess in a production environment. Is there a way to
get around this problem with oversized words?
Kind regards
Markus
> -Ursprüngliche Nachricht-
> Von: Oleg Bartunov [mailto:[EMAIL PROTECTED]
> Gesendet: Freitag, 21. November 2003 15:13
> An: Markus Wollny
> Cc: [
On Fri, 21 Nov 2003, Markus Wollny wrote:
> Hello!
>
> > Von: Oleg Bartunov [mailto:[EMAIL PROTECTED]
> > Gesendet: Freitag, 21. November 2003 13:06
> > An: Markus Wollny
> > Cc: [EMAIL PROTECTED]
> >
> > Word length is limited by 2K. What's exactly the word
> > tsearch2 complained on ?
> > 'Llanf
Hello!
> Von: Oleg Bartunov [mailto:[EMAIL PROTECTED]
> Gesendet: Freitag, 21. November 2003 13:06
> An: Markus Wollny
> Cc: [EMAIL PROTECTED]
>
> Word length is limited by 2K. What's exactly the word
> tsearch2 complained on ?
> 'Llanfairpwllgwyngyllgogerychwyrndrobwantysiliogogogoch'
> i
On Fri, 21 Nov 2003, Markus Wollny wrote:
> Hello!
>
> I'm currently testing deployment of tsearch2 on our forum table. The
> table is huge in itself - some 2GB of data without the indexes. I have
> got PostgreSQL 7.4RC2 running on a test machine, installed tsearch2 to
> my database, added the new
Hello!
I'm currently testing deployment of tsearch2 on our forum table. The
table is huge in itself - some 2GB of data without the indexes. I have
got PostgreSQL 7.4RC2 running on a test machine, installed tsearch2 to
my database, added the new column to the table and tried to update it in
the rec
