pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: subscriber@blackbrook.org
Subject: documentation clarification of tsvector length limitation
Date: Thu, 09 Feb 2023 23:37:31 +0000
Message-ID: <167598585168.224484.382764866201320@wrigleys.postgresql.org> (raw)

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.)


Message-ID: <167598585168.224484.382764866201320@wrigleys.postgresql.org>
Permalink:  ../167598585168.224484.382764866201320@wrigleys.postgresql.org/
Also on:    postgresql.org/message-id/167598585168.224484.382764866201320@wrigleys.postgresql.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: noreply@postgresql.org, pgsql-docs@lists.postgresql.org, subscriber@blackbrook.org
  Subject: Re: documentation clarification of tsvector length limitation
  In-Reply-To: <167598585168.224484.382764866201320@wrigleys.postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox