Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vZbXa-00FHYf-2S for pgsql-hackers@arkaria.postgresql.org; Sat, 27 Dec 2025 21:09:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vZbXY-00CDfs-1H for pgsql-hackers@arkaria.postgresql.org; Sat, 27 Dec 2025 21:09:33 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vZbXX-00CDfj-33 for pgsql-hackers@lists.postgresql.org; Sat, 27 Dec 2025 21:09:32 +0000 Received: from mail-ej1-x630.google.com ([2a00:1450:4864:20::630]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vZbXV-0038YG-1s for pgsql-hackers@lists.postgresql.org; Sat, 27 Dec 2025 21:09:32 +0000 Received: by mail-ej1-x630.google.com with SMTP id a640c23a62f3a-b832522b47cso270934966b.0 for ; Sat, 27 Dec 2025 13:09:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1766869767; x=1767474567; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=PASxsoP9w+Ipm5cQpRqTg2hL5XRFRRPBh4XzsB6dX5k=; b=eU2mcG9x73zE66E6xH82Ztju5r85JgxjMg73vYsXAvDwjSMK610w1sdUdscuC0WH11 axEotzOfhPM9vwMXEUKT0Z0rqhkQJZ2Qrz4Qd9mBl85uDcDFnk+gVUTAkp+a0tnpRhDi ajjQwEoR5Ih1caOotHsPpw0q1GcJJxlAA6EA1Hcrh2cM/lZUSf8d2Wiewv8B+HeeIhu4 5Z5OL8X6CHP0eNJmy8t8pFTeb3rIFZRllYkZHtzH8g5zMQ6042ArgGwB3ux1iaZzk2x2 VnnazXETj6+HKdgehhC4D+ZdTZ3wU8TmZ1E/PHFCkxwnLi4fxRgM8GsM5zA12Oka+UU4 fSVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1766869767; x=1767474567; h=to:subject:message-id:date:from:mime-version:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=PASxsoP9w+Ipm5cQpRqTg2hL5XRFRRPBh4XzsB6dX5k=; b=QppflQh6DsWfnpPe851KOCGETMJ/3EolpAoxfrpOKLFpnuI36JLjM9czuGmN7zpyu3 y3oE3zFCEcEXZJgHJHyoEMrVHP/McmbNOLxd4fvOzn+SIoa2/2PhkwFDkKWnWaPCQSHO KsckC7AQPjlhU7yMSoIVWDopWi+XqCdAooPpnX26HOkcKX7OBtm4mjBRZkYVIUcy7d6t OCkM6fVqFcJih6We09UjvZTs8lgHvvXRq4stfcm7PK3mH8A+nyZEDvq0wR+atNA/P47L zmNHC1+xSWKrJ6s4ysc1RP1XVlZqkEQYhWyX87rwXQ6TGgW7x22g2XLg3Bk/H/q4eWWr 4jmg== X-Gm-Message-State: AOJu0YyFHcFQ+nhzCLwcU8bTZ3+RivqpiXbA2JkQeQWPCZpZ7KLiHpnt h+2rzAbn/puL047bb/b8KTHqd6oI2+NEEEHRN215YXZwRcD7pac/bqD8y1ffywuTAWvIhq2CAU5 J3KylvGtnMs7DanO57VmJpI/ZsRjtiLECoCSJ X-Gm-Gg: AY/fxX5oWLM26QB1hsi24nov747fRtt16r/3xXGynpvxRv/+1ljYSR5lWnjBthGPpks 08prZcszxFI6SjeExGwUJodPverczzXI+xZjEKF5ahFNwNYC0XTnaLzk3vBxryKRvQSGj7SvaBD qY6ptT6OyyKSud8ySLLB4TLgnwj6o8zayHo1yEnvd0/MqD7TPAkPoFxf4tKciIGYl3aaEwIOewD sh/AJ9R4zERkPYONZ31yFaxzYoeH1MbuEFkz8touIsi9v2s0LYaqqimlEAvOWQ+HxCttN842Xrp EzVLznJyMrsLjyCdh6ItukD6cBbNUEdNRqCoLdWk X-Google-Smtp-Source: AGHT+IHPbtycoFyJI/BRrg9+46RcnGehZs0PP0xEQeqhbgM77MZcsl19yixOyAOgfrmlk/GF8HtEECI5V6dZF/zyfQo= X-Received: by 2002:a17:906:c108:b0:b6d:6d66:e8e9 with SMTP id a640c23a62f3a-b80371f98e6mr2937479566b.61.1766869766573; Sat, 27 Dec 2025 13:09:26 -0800 (PST) MIME-Version: 1.0 From: Dharin Shah Date: Sat, 27 Dec 2025 22:09:14 +0100 X-Gm-Features: AQt7F2r0KqLXBD5-frsWcv0rwuDqXOmhz7jL3dIsSQEP-KNB9yL12-FvIzIWYjA Message-ID: Subject: [PATCH][DOC][MINOR] Fix incorrect lexeme limit in textsearch docs To: pgsql-hackers@lists.postgresql.org Content-Type: multipart/mixed; boundary="000000000000cd42f80646f56cbd" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000cd42f80646f56cbd Content-Type: multipart/alternative; boundary="000000000000cd42f60646f56cbb" --000000000000cd42f60646f56cbb Content-Type: text/plain; charset="UTF-8" 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.