| From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Cc: | subscriber(at)blackbrook(dot)org |
| Subject: | documentation clarification of tsvector length limitation |
| Date: | 2023-02-09 23:37:31 |
| Message-ID: | 167598585168.224484.382764866201320@wrigleys.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/15/textsearch-limitations.html
Description:
I'm suggesting a documentation clarification to the statement "The length of
a tsvector (lexemes + positions) must be less than 1 megabyte" from the page
https://www.postgresql.org/docs/current/textsearch-limitations.html.
It's not clear what "length" here means, especially in light of the
parenthetical "(lexemes + positions)". Only lexemes and positions but not
weights?
The length() function on a tsvector gives the lexeme count, is that the
limit here? Or would the storage space returned with the pg_column_size
function give the length to which this limitation applies? (Trying this out,
it gives numbers somewhat larger that what I get when looking at the text
representations I see when querying the tsvector column.)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Doc comments form | 2023-02-10 18:09:17 | Getting out of copy out mode |
| Previous Message | Erik Wienhold | 2023-02-02 08:52:45 | Re: 1.3 Creating a database - windows 10x64 |