From 40adfc381b50c29014d05ee497c424a8ee7ac533 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Sun, 16 Aug 2026 12:15:26 -0400 Subject: [PATCH v1 2/2] Clean up documentation about text search datatype limits. textsearch.sgml neglected to mention that the MAXSTRPOS total-length limit applies to tsquery as well as tsvector. It also claims that there is a 32K limit on the total number of nodes in a tsquery, which is wrong. (I suspect that QueryOperator.left may once have been int16, which would give rise to such a limit. But it's uint32 now, so you'd hit the 1GB varlena limit well before overflowing that.) While at it, re-order the bullet points into an order that makes more sense, to me anyway. Reported-by: Claude Code (via Noah Misch) Author: Tom Lane Backpatch-through: 14 --- doc/src/sgml/textsearch.sgml | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/doc/src/sgml/textsearch.sgml b/doc/src/sgml/textsearch.sgml index d6d2ddeaacc..2f3a76bef1e 100644 --- a/doc/src/sgml/textsearch.sgml +++ b/doc/src/sgml/textsearch.sgml @@ -4046,24 +4046,24 @@ Parser: "pg_catalog.default" The length of each lexeme must be less than 2 kilobytes - The length of a tsvector (lexemes + positions) must be - less than 1 megabyte + No more than 256 positions per lexeme Position values in tsvector must be greater than 0 and no more than 16,383 - The match distance in a <N> - (FOLLOWED BY) tsquery operator cannot be more than - 16,384 + The length of a tsvector's data (lexemes + positions) + must be less than 1 megabyte - No more than 256 positions per lexeme + The length of a tsquery's data (lexemes only) + must be less than 1 megabyte - The number of nodes (lexemes + operators) in a tsquery - must be less than 32,768 + The match distance in a <N> + (FOLLOWED BY) tsquery operator cannot be more than + 16,384 -- 2.52.0