Re: [PATCH][DOC][MINOR] Fix incorrect lexeme limit in textsearch docs

From: Aditya Gollamudi <adigollamudi(at)gmail(dot)com>
To: surya poondla <suryapoondla4(at)gmail(dot)com>
Cc: Dharin Shah <dharinshah95(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH][DOC][MINOR] Fix incorrect lexeme limit in textsearch docs
Date: 2026-01-16 09:35:40
Message-ID: CAD-KL_GXFMc-ty9ww94HjdCs-WdbgG2oSLWvnjqztWFBxPq1vA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jan 9, 2026 at 2:01 PM surya poondla <suryapoondla4(at)gmail(dot)com>
wrote:

> Hi Dharin,
>
> I looked at your patch, it looks good.
>
> In the code, I couldn’t find any 2^64 bound on the lexeme count, so
> removing that makes sense.
> The added sentence about distinct lexeme count seems to overlap with the
> existing description of tsvector limits, so I’m not sure it adds much new
> information.
>
> -Surya Poondla
>

+1 on this patch, I was also a bit confused on this part of the
documentation. All I could conclude was that the number of lexemes in a
tsvector was limited by existing tsvector limits. I agree with Surya's
comment about the overlap, I think this patch should only remove the line
about the 2^64 bound. Patch applies cleanly!

Adi Gollamudi

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message jian he 2026-01-16 09:52:30 heap_create_with_catalog comments
Previous Message Michael Banck 2026-01-16 09:29:59 Re: Add missing JIT inline pass for llvm>=17