Summary
Exporting an already populated internal DB used by Airbyte to an external DB and facing errors. Steps involve taking a dump of the internal DB, importing it into an external Postgres server, and updating the .env file with new DB host, name, and user.
Question
Hi I am trying to export an already populated internal DB that airbyte uses to an external db. Is it a good idea to do it ? As Ive been facing different kinds of errors
Steps I did.
- Take a dump of the internal db
- Import that dump in an external postgres server
- Change .env file of airbyte to the new db host , db name, and user to connect
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.