Summary
Airbyte becomes unresponsive when using an external Postgres v16 database. Conflicting information on whether Airbyte supports Postgres 13 or higher. Seeking clarity on the support for Postgres versions in the latest Airbyte version.
Question
Hi community, we are using airbyte version 0.50.50, with an external postgres v16 database to store the airbyte configuration. However, airbyte becomes unresponsive every 2 weeks or so. A team member of mine claims that this because only postgres 13 is supported.
I read conflicting messages that only postgres 13 is supported. The https://docs.airbyte.com/operator-guides/configuring-airbyte-db#connecting-to-an-external-postgres-database|documentation does not specify which version and this github https://github.com/airbytehq/airbyte/issues/38182|issue is conclusive either.
I prefer not to downgrade the database because postgres 13 will be end of life this year.
Can anybody here perhaps provide clarity. Does the latest version of airbyte support postgres 13 or higher?
Thanks!
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.
Join the conversation on Slack
["airbyte", "postgres-13", "external-database", "support", "documentation"]
Hi <@U07AVQSTCPJ> It actually supports well. I have opened the pull request and removed the limitation in the doc https://github.com/airbytehq/airbyte/pull/39510
I succeed with a clean Postgres 16.3, I have published all deployment codes using Terraform at https://github.com/hongbo-miao/hongbomiao.com/issues/17463#issuecomment-2180242019 
And all issues I met and solutions as well in first comment 
The only thing is Airbyte copied temporalio/auto-setup old script instead of pointing to it, and it has not been updated to latest version yet, so current workaround solution is disabling rds.force_ssl (I posted details at https://github.com/airbytehq/airbyte/issues/39636) Anyway my deployment codes mentioned this issue and covered it as well.
Hope it helps!
As you’ll see in search, this has come up several times here. I know of people using Postgres 14, 15, and 16 (we’re on 15 currently) without any issues.
As came up in a previous thread, this note was based on a requirement of a component (I believe Temporal), but it’s been difficult for everyone to discern whether that upstream issue has been cleared . . . so I think it’s been a bit more wait and see.
I will tell you from our experience that the 0.50.x branch isn’t nearly as stable as current builds in our experience, so I would highly recommend upgrading before chasing phantom Postgres-related issues 
Hi Justin,
Thank you for replying to my question and sharing your experience . I will upgrade our Airbyte version as you suggested and monitor if it will improve.