> For the complete documentation index, see [llms.txt](https://docs.elimity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elimity.com/reference-manual/v3.44.5/installation/postgresql-database.md).

# PostgreSQL database

The Elimity Insights server manages all of its persistent data in a PostgreSQL database. For SaaS customers we perform the setup and maintenance of PostgreSQL servers behind the scenes. These installation instructions are mainly useful for on-prem deployments. We strongly recommend using your cloud provider's DBaaS offering to set up a PostgreSQL database. More specifically, Elimity Insights servers officially support PostgreSQL 15.x and 17.x. The `btree_gist`, `pgcrypto` and `plv8` extensions must also be available. If using your cloud provider's DBaaS offering is not an option, then installing PostgreSQL manually on e.g. a Linux VM is also possible.

We heavily recommend creating a dedicated database and user for Elimity Insights. More specifically, we suggest the following steps:

1. Create a dedicated PostgreSQL user with no privileges and a strong authentication mechanism
2. Create a dedicated database and assign the new user as its owner

{% hint style="danger" %}
Please note that v3.44 is the last release that will support PostgreSQL 15.
{% endhint %}


---

# 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.elimity.com/reference-manual/v3.44.5/installation/postgresql-database.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.