Issue with Postgres connector after accidental upgrade in Airbyte

Summary

The user accidentally clicked the ‘upgrade all’ button in the ‘Settings’ tab of Airbyte, causing issues with the Postgres connector. Syncs do not go past the upgrade time. User is seeking a way to get the connectors running again without immediately upgrading the software.


Question

I’m running Airbyte version 0.44.12 and running it on Kubernetes using helm chart version v0.45.31. I recently was looking at the “Settings” tab and accidentally clicked the “upgrade all” button while I was there. This seems to have broken my Postgres connector. I can occasionally get a sync to complete, but when it does, it does not sync any data past the time when I clicked the “upgrade all” button. My production system is currently down and I haven’t had any luck setting up a new connector to get it working. Most troubleshooting online resources indicate the next step would be to fully upgrade the software, which I’m willing to do but can’t do immediately. Is there any way to get my connectors running again?



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-connector", "upgrade-all", "sync", "troubleshooting"]