> For the complete documentation index, see [llms.txt](https://docs.secoda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secoda.co/integrations/databases/postgres-integration/postgres-metadata.md).

# Postgres Metadata Extracted

### Metadata pulled

Secoda pulls the following metadata from Postgres:

* Tables and Views
  * Name
  * Description
  * Last Updated Timestamp
  * Schema
  * Database
* View Definition (Table Creation Query)
* Columns
  * Name
  * Description
  * Type
  * Foreign Key
  * Primary Key
* Column Profile
  * Min
  * Max
  * Median
  * STD Deviation
  * Value Distribution
  * Statistic Value Count
  * Percent Filled
  * Unique
* Lineage
  * Postgres Table <-> Postgres Table
  * Postgres View <-> Postgres Table
  * Postgres View <-> Postgres Column
  * Postgres Column <-> Postgres Column
  * Postgres Table/View <-> Tables from other sources
  * Postgres Table/View <-> Dashboards from other sources
  * Postgres Table/View <-> Jobs from other sources
* Preview of first 50 rows (Optional)

### Metadata pushed <a href="#metadata-pushed" id="metadata-pushed"></a>

If enabled, Secoda pushes the following metadata to Postgres:

* Tables
  * Description
* Columns
  * Description


---

# 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.secoda.co/integrations/databases/postgres-integration/postgres-metadata.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.