> 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/15/internals/54.-system-views/pg_user_mappings.md).

# 54.34. pg\_user\_mappings

## 54.34. pg\_user\_mappings

The view `pg_user_mappings` provides access to information about user mappings. This is essentially a publicly readable view of [`pg_user_mapping`](/15/internals/system-catalogs/pg_user_mapping.md) that leaves out the options field if the user has no rights to use it.

**Table 54.34. `pg_user_mappings` Columns**

| <p>Column Type</p><p>Description</p>                                                                                                                                                                                                       |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| <p><code>umid</code> <code>oid</code> (references <a href="/15/internals/system-catalogs/pg_user_mapping.md"><code>pg\_user\_mapping</code></a>.<code>oid</code>)</p><p>OID of the user mapping</p>                                        |
| <p><code>srvid</code> <code>oid</code> (references <a href="/15/internals/system-catalogs/pg_foreign_server.md"><code>pg\_foreign\_server</code></a>.<code>oid</code>)</p><p>The OID of the foreign server that contains this mapping</p>  |
| <p><code>srvname</code> <code>name</code> (references <a href="/15/internals/system-catalogs/pg_foreign_server.md"><code>pg\_foreign\_server</code></a>.<code>srvname</code>)</p><p>Name of the foreign server</p>                         |
| <p><code>umuser</code> <code>oid</code> (references <a href="/15/internals/system-catalogs/pg_authid.md"><code>pg\_authid</code></a>.<code>oid</code>)</p><p>OID of the local role being mapped, or zero if the user mapping is public</p> |
| <p><code>usename</code> <code>name</code></p><p>Name of the local user to be mapped</p>                                                                                                                                                    |
| <p><code>umoptions</code> <code>text\[]</code></p><p>User mapping specific options, as “keyword=value” strings</p>                                                                                                                         |

To protect password information stored as a user mapping option, the `umoptions` column will read as null unless one of the following applies:

* current user is the user being mapped, and owns the server or holds `USAGE` privilege on it
* current user is the server owner and mapping is for `PUBLIC`
* current user is a superuser

***

原文：[PostgreSQL 15.19 Documentation](/15/internals/54.-system-views/pg_user_mappings.md)（英文原文，待翻譯）


---

# 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/15/internals/54.-system-views/pg_user_mappings.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.