> 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/16/internals/b-tree-indexes/introduction.md).

# 67.1. Introduction

PostgreSQL 實作了標準 btree（多向平衡樹）索引資料結構。任何可以按明確定義的線性順序排序的資料型別都可以透過 btree 索引進行索引。唯一的限制是索引數目不能超過頁面的大約三分之一（如果有 TOAST 壓縮的話，指的是壓縮後的大小）。

因為每個 btree 運算子類對其資料型別強加排序順序，所以 btree 運算子類（或者，實際上，運算子家族）已經被用作 PostgreSQL 對排序的一般表示和理解。 因此，他們獲得了一些超出僅支持 btree 索引所需的功能，並且系統中與 btree AM 相距甚遠的部分使用了它們。


---

# 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/16/internals/b-tree-indexes/introduction.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.