mirror of
https://github.com/postgres/postgres.git
synced 2026-04-05 01:07:27 -04:00
960382e3e9
This is nonsense on its face, since the textsearch parsing logic generally uses int32 to count words (see, eg, struct ParsedText). Not to mention that we don't support input strings larger than 1GB. The actual limitation of interest is documented nearby: a tsvector can't be larger than 1MB, thanks to 20-bit offset fields within it (see WordEntry.pos). That constrains us to well under 256K lexemes per tsvector, depending on how many positions are stored per lexeme. It seems sufficient therefore to just remove the bit about number of lexemes. Author: Dharin Shah <dharinshah95@gmail.com> Discussion: https://postgr.es/m/CAOj6k6d0YO6AO-bhxkfUXPxUi-+YX9-doh2h5D5z0Bm8D2w=OA@mail.gmail.com |
||
|---|---|---|
| .. | ||
| src | ||
| KNOWN_BUGS | ||
| Makefile | ||
| MISSING_FEATURES | ||
| TODO | ||