> 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/internals/views/view-pg-seclabels.md).

# 53.23. pg\_seclabels \#

The view `pg_seclabels` provides information about security labels. It as an easier-to-query version of the [`pg_seclabel`](/internals/catalogs/catalog-pg-seclabel.md) catalog.

**Table 53.23. `pg_seclabels` Columns**

| <p>Column Type</p><p>Description</p>                                                                                                                                                                                                                   |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| <p><code>objoid</code> <code>oid</code> (references any OID column)</p><p>The OID of the object this security label pertains to</p>                                                                                                                    |
| <p><code>classoid</code> <code>oid</code> (references <a href="/pages/b1fii6hWVNacZFXaxWON"><code>pg\_class</code></a>.<code>oid</code>)</p><p>The OID of the system catalog this object appears in</p>                                                |
| <p><code>objsubid</code> <code>int4</code></p><p>For a security label on a table column, this is the column number (the <code>objoid</code> and <code>classoid</code> refer to the table itself). For all other object types, this column is zero.</p> |
| <p><code>objtype</code> <code>text</code></p><p>The type of object to which this label applies, as text.</p>                                                                                                                                           |
| <p><code>objnamespace</code> <code>oid</code> (references <a href="/pages/p7uH9oRd2ZTbQCzy1qKB"><code>pg\_namespace</code></a>.<code>oid</code>)</p><p>The OID of the namespace for this object, if applicable; otherwise NULL.</p>                    |
| <p><code>objname</code> <code>text</code></p><p>The name of the object to which this label applies, as text.</p>                                                                                                                                       |
| <p><code>provider</code> <code>text</code> (references <a href="/pages/YZwjcpaEXdZPFAOdxrdW"><code>pg\_seclabel</code></a>.<code>provider</code>)</p><p>The label provider associated with this label.</p>                                             |
| <p><code>label</code> <code>text</code> (references <a href="/pages/YZwjcpaEXdZPFAOdxrdW"><code>pg\_seclabel</code></a>.<code>label</code>)</p><p>The security label applied to this object.</p>                                                       |

<br>

***

原文：[PostgreSQL 18.6 Documentation](https://www.postgresql.org/docs/18/view-pg-seclabels.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/internals/views/view-pg-seclabels.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.
