> 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-transforms.md).
# 35.55. transforms \#
The view `transforms` contains information about the transforms defined in the current database. More precisely, it contains a row for each function contained in a transform (the “from SQL” or “to SQL” function).
**Table 35.53. `transforms` Columns**
| Column Type
Description
|
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| udt\_catalog sql\_identifier
Name of the database that contains the type the transform is for (always the current database)
|
| udt\_schema sql\_identifier
Name of the schema that contains the type the transform is for
|
| udt\_name sql\_identifier
Name of the type the transform is for
|
| specific\_catalog sql\_identifier
Name of the database containing the function (always the current database)
|
| specific\_schema sql\_identifier
Name of the schema containing the function
|
| specific\_name sql\_identifier
The “specific name” of the function. See Section 35.45 for more information.
|
| group\_name sql\_identifier
The SQL standard allows defining transforms in “groups”, and selecting a group at run time. PostgreSQL does not support this. Instead, transforms are specific to a language. As a compromise, this field contains the language the transform is for.
|
| transform\_type character\_data
FROM SQL or TO SQL
|
***
原文：[PostgreSQL 18.6 Documentation](https://www.postgresql.org/docs/18/infoschema-transforms.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-transforms.md?ask=&goal=
```
`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.