public inbox for [email protected]
help / color / mirror / Atom feedFrom: Dharin Shah <[email protected]>
To: [email protected]
Subject: Re: [PATCH][DOC][MINOR] Fix incorrect lexeme limit in textsearch docs
Date: Fri, 2 Jan 2026 12:38:25 +0100
Message-ID: <CAOj6k6cr+9HA2Dd=iQvZWPbmSgd2eV-8Vk2=hP-rouwa+gLVfg@mail.gmail.com> (raw)
In-Reply-To: <CAOj6k6d0YO6AO-bhxkfUXPxUi-+YX9-doh2h5D5z0Bm8D2w=OA@mail.gmail.com>
References: <CAOj6k6d0YO6AO-bhxkfUXPxUi-+YX9-doh2h5D5z0Bm8D2w=OA@mail.gmail.com>
Hello,
Gentle ping on the textsearch docs patch. Happy to address any feedback
Thanks,
Dharin
On Sat, Dec 27, 2025 at 10:09 PM Dharin Shah <[email protected]> wrote:
> Hello,
>
> A minor doc patch for this page
> https://www.postgresql.org/docs/current/textsearch-limitations.html
> and this line
>
> *- The number of lexemes must be less than 2^64*
>
> Docs wrongly claim "lexemes must be < 2^64" but the actual constraint is
> 1 MB total storage (MAXSTRPOS), and no 2^64 check exists in the code.
>
> From src/include/tsearch/ts_type.h:
>
>> #define MAXSTRPOS ( (1<<20) - 1) // 1,048,575 bytes
>>
>> typedef struct {
>> int32 size; // number of lexemes
>> ...
>> } TSVectorData;
>
>
> The attached patch:
> - Removes the incorrect 2^64 claim
> - Clarifies this means "distinct lexemes in a single tsvector value"
>
> Thanks,
> Dharin
>
view thread (2+ messages) latest in thread
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: [email protected]
Cc: [email protected], [email protected]
Subject: Re: [PATCH][DOC][MINOR] Fix incorrect lexeme limit in textsearch docs
In-Reply-To: <CAOj6k6cr+9HA2Dd=iQvZWPbmSgd2eV-8Vk2=hP-rouwa+gLVfg@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox