[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-admin
Subject:    [ADMIN] ts_vector workaround for  - No more than 256 positions per lexeme
From:       avni <avni () avni ! net>
Date:       2013-10-10 20:09:17
Message-ID: 1381435757687-5774106.post () n5 ! nabble ! com
[Download RAW message or body]

Hi - I am trying to build a search engine where frequency of a term in the
search document is very important and I need ts_vector to be able to support
more than 256 positions per lexeme (up to 2000 at least). Does anyone know
of a workaround to this limit or how I could build one? 

Thanks in advance,
Avni



--
View this message in context: \
http://postgresql.1045698.n5.nabble.com/ts-vector-workaround-for-No-more-than-256-positions-per-lexeme-tp5774106.html
 Sent from the PostgreSQL - admin mailing list archive at Nabble.com.


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin


[prev in list] [next in list] [prev in thread] [next in thread]