| From: | Dharin Shah <dharinshah95(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [PATCH][DOC][MINOR] Fix incorrect lexeme limit in textsearch docs |
| Date: | 2026-01-02 11:38:25 |
| Message-ID: | CAOj6k6cr+9HA2Dd=iQvZWPbmSgd2eV-8Vk2=hP-rouwa+gLVfg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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 <dharinshah95(at)gmail(dot)com> 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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matheus Alcantara | 2026-01-02 12:11:16 | Re: Include extension path on pg_available_extensions |
| Previous Message | Soumya S Murali | 2026-01-02 10:09:40 | Re: 001_password.pl fails with --without-readline |