Docs: update pg13 requirement for external db (#34858)

airbytehq · Feb 5, 2024 · ee39d40 · ee39d40
1 parent c7c51ea
commit ee39d40
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 0 deletions.
diff --git a/docs/enterprise-setup/implementation-guide.md b/docs/enterprise-setup/implementation-guide.md
@@ -105,6 +105,10 @@ To configure basic auth (deploy without SSO), remove the entire `auth:` section
 
 For Self-Managed Enterprise deployments, we recommend using a dedicated database instance for better reliability, and backups (such as AWS RDS or GCP Cloud SQL) instead of the default internal Postgres database (`airbyte/db`) that Airbyte spins up within the Kubernetes cluster.
 
+:::info
+Currently, Airbyte requires connection to a Postgres 13 instance.
+:::
+
 We assume in the following that you've already configured a Postgres instance:
 
 <details>

diff --git a/docs/operator-guides/configuring-airbyte-db.md b/docs/operator-guides/configuring-airbyte-db.md
@@ -25,6 +25,10 @@ If you need to interact with it, for example, to make back-ups or perform some c
 
 ## Connecting to an External Postgres database
 
+:::info
+Currently, Airbyte requires connection to a Postgres 13 instance.
+:::
+
 Let's walk through what is required to use a Postgres instance that is not managed by Airbyte. First, for the sake of the tutorial, we will run a new instance of Postgres in its own docker container with the command below. If you already have Postgres running elsewhere, you can skip this step and use the credentials for that in future steps.
 
 ```bash