> For the complete documentation index, see [llms.txt](https://docs.postgresql.tw/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.postgresql.tw/13/the-sql-language/12.-quan-wen-jian-suo/12.11.-gong-neng-xian-zhi.md).

# 12.11. 功能限制

The current limitations ofPostgreSQL's text search features are:

* The length of each lexeme must be less than 2K bytes
* The length of a`tsvector`(lexemes + positions) must be less than 1 megabyte
* The number of lexemes must be less than 264
* 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
* No more than 256 positions per lexeme
* The number of nodes (lexemes + operators) in a`tsquery`must be less than 32,768

For comparison, thePostgreSQL8.1 documentation contained 10,441 unique words, a total of 335,420 words, and the most frequent word“postgresql”was mentioned 6,127 times in 655 documents.

Another example — thePostgreSQLmailing list archives contained 910,989 unique words with 57,491,343 lexemes in 461,020 messages.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.postgresql.tw/13/the-sql-language/12.-quan-wen-jian-suo/12.11.-gong-neng-xian-zhi.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.