> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/app/setting-up-your-database/postgres/postgresql-system-requirements.md).

# System requirements for PostgreSQL

{% hint style="info" %}
If you want to use a version that Structural does not support, contact Tonic.ai.
{% endhint %}

{% hint style="info" %}
**Versions for which Structural support is ending**

As of April 1, 2026, Structural will not support the following versions of PostgreSQL:

* PostgreSQL 10
* PostgreSQL 11
* PostgreSQL 12
* PostgreSQL 13

The database provider also no longer supports these versions.
{% endhint %}

Tonic Structural supports PostgreSQL 14 through PostgreSQL 18.

You can also use the PostgreSQL data connector to connect to an Amazon Aurora database.

Source and destination databases should use the same database version and must have the same extensions installed.

At the very least, the destination database version cannot be older than the source database version. For example, if the source database uses PostgreSQL 12.8, then the destination database cannot use a lower version such as PostgreSQL 12.4.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tonic.ai/app/setting-up-your-database/postgres/postgresql-system-requirements.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 `build a script that syncs our docs to a CMS` 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.