> For the complete documentation index, see [llms.txt](https://docs.bindplane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bindplane.com/deployment/virtual-machine/bindplane/postgresql.md).

# PostgreSQL

[PostgreSQL](https://www.postgresql.org/) is used by Bindplane for storing data such as collector metadata and configurations.

### Prerequisites

#### 1. Postgres Sizing

Postgres can be scaled vertically based on the number of managed collectors. See the [Postgresql Sizing](/deployment/virtual-machine/bindplane/postgresql/postgres-sizing.md) documentation for sizing details.

#### 2. Postgres Installation

Postgres installation must be done before installing Bindplane. See the [Postgres Installation](/deployment/virtual-machine/bindplane/postgresql/postgres-installation.md) documentation for more information.

#### 3. Postgres Configuration

After installing Postgres, you will need to configure it. See the [Postgres Configuration](/deployment/virtual-machine/bindplane/postgresql/postgres-configuration.md) documentation for more information.

### Bindplane Configuration

For a list of supported Bindplane PostgreSQL configuration options, see the [Postgres Configuration](/configuration/bindplane.md#postgres) section in the configuration documentation.


---

# 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.bindplane.com/deployment/virtual-machine/bindplane/postgresql.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.