Hi Jonathan,
Check out this potential fix/extension
https://github.com/postgrespro/tsvector2
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
What if we just didn’t use positional arguments at all? I.e. we just populate
the tsvector with lexemes only?
> On Jun 20, 2018, at 10:49 AM, Tom Lane wrote:
>
> Jonathan Marks writes:
>> ... we run into the max tsvector length requirement "The length of a
>> tsvector (lexemes + positions) mu
Jonathan Marks writes:
> ... we run into the max tsvector length requirement "The length of a tsvector
> (lexemes + positions) must be less than 1 megabyte”
> Is there any way to disable or increase that limit in Postgres 10.3?
No; it's forced by the representation used for tsvector, which stor
Hi folks —
We utilize Postgres’ full text search system pretty heavily in our team’s
operations and often index tens of millions of records with varying lengths of
text. In most cases, the text we need to index is pretty short (no more than.
hundreds of words) but in rare cases a single record
