Re: tsvector field length limitation - Mailing list pgsql-general

From Jonathan Marks
Subject Re: tsvector field length limitation
Date
Msg-id 09ECA82E-C221-4D79-B2FC-5493F330B6EB@gmail.com
Whole thread Raw
In response to Re: tsvector field length limitation  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: tsvector field length limitation  (AJG <ayden@gera.co.nz>)
List pgsql-general
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 <tgl@sss.pgh.pa.us> wrote:
>
> Jonathan Marks <jonathanaverymarks@gmail.com> writes:
>> ... we run into the max tsvector length requirement "The length of a tsvector (lexemes + positions) must be less
than1 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 stores
> lexeme offsets in 20-bit fields (cf WordEntry in
> src/include/tsearch/ts_type.h).  Perhaps that was short-sighted but
> I don't foresee it changing anytime soon.  You'd more or less need
> a whole new datatype ("bigtsvector"?) to make it happen.
>
>             regards, tom lane



pgsql-general by date:

Previous
From: Igor Korot
Date:
Subject: Re: Is there a way to be notified on the CREATE TABLE execution?
Next
From: Alban Hertroys
Date:
Subject: Re: Is postorder tree traversal possible with recursive CTE's?