> 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/client-interfaces/information-schema/infoschema-schema.md).

# 35.1. The Schema \#

資訊結構描述本身是一個名為 `information_schema` 的 schema。此 schema 會自動 存在於所有資料庫中。它的擁有者是叢集的初始資料庫使用者，該使用者自然擁有此 schema 的所有權限，包括刪除它的能力（不過這樣能節省的空間微乎其微）。

預設情況下，資訊結構描述不在 schema 搜尋路徑中，因此必須以限定名稱存取其中 的所有物件。資訊結構描述中的某些物件名稱很通用，可能也會出現在使用者應用程式 中；若要將資訊結構描述加入搜尋路徑，應特別小心。

***

【[PostgreSQL 18.6 文件](https://www.postgresql.org/docs/18/infoschema-schema.html)】


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.postgresql.tw/client-interfaces/information-schema/infoschema-schema.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.