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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Aditya Gollamudi <adigollamudi(at)gmail(dot)com>
Cc: surya poondla <suryapoondla4(at)gmail(dot)com>, 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-03-26 22:02:26
Message-ID: 1048391.1774562546@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Aditya Gollamudi <adigollamudi(at)gmail(dot)com> writes:
> +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!

What I'm inclined to do is just drop that <listitem> entirely,
since it's implied by the 1MB space limit. The patch as-submitted
accomplishes about the same thing, but takes more words to do it.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2026-03-26 22:03:15 Re: Clean up NamedLWLockTranche stuff
Previous Message Masahiko Sawada 2026-03-26 22:01:04 Re: Add uuid_to_base32hex() and base32hex_to_uuid() built-in functions