public inbox for [email protected]  

help / color / mirror / Atom feed

From: Aditya Gollamudi <[email protected]>
To: surya poondla <[email protected]>
Cc: Dharin Shah <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH][DOC][MINOR] Fix incorrect lexeme limit in textsearch docs
Date: Fri, 16 Jan 2026 01:35:40 -0800
Message-ID: <CAD-KL_GXFMc-ty9ww94HjdCs-WdbgG2oSLWvnjqztWFBxPq1vA@mail.gmail.com> (raw)
In-Reply-To: <CAOVWO5ri14VWdJh+tYt2d5O0VAbZbEhU1C=x-jaxE8qBYgLoUA@mail.gmail.com>
References: <CAOj6k6d0YO6AO-bhxkfUXPxUi-+YX9-doh2h5D5z0Bm8D2w=OA@mail.gmail.com>
	<CAOVWO5ri14VWdJh+tYt2d5O0VAbZbEhU1C=x-jaxE8qBYgLoUA@mail.gmail.com>

On Fri, Jan 9, 2026 at 2:01 PM surya poondla <[email protected]>
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

view thread (3+ 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], [email protected], [email protected]
  Subject: Re: [PATCH][DOC][MINOR] Fix incorrect lexeme limit in textsearch docs
  In-Reply-To: <CAD-KL_GXFMc-ty9ww94HjdCs-WdbgG2oSLWvnjqztWFBxPq1vA@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