Yes, Airbyte stores the state of connections in an internal Postgres database. When you update the version of Airbyte running inside Docker, the state of the connections should be preserved, as long as the internal database is not deleted or corrupted during the update process. To ensure that the state is properly restored after an update, you can follow these steps: 1. Backup the Internal Database: Before performing the update, it's a good practice to back up the internal Postgres database where the state is stored. You can access the database using the following command:

bash     docker exec -ti airbyte-db psql -U docker -d airbyte

You can then use standard Postgres backup commands to create a backup of the database. 2. Update Airbyte: Proceed with updating Airbyte to the new version. Ensure that the Docker volumes are not removed during this process, as they contain the database data. 3. Verify the State: After the update, you can verify that the state has been restored by querying the state table in the internal database:

bash     SELECT * FROM state;

For more detailed information on how Airbyte persists state and how to access the internal database, you can refer to the [Airbyte Protocol documentation](https://docs.airbyte.com/understanding-airbyte/airbyte-protocol) and the [tutorial on incremental data synchronization](https://airbyte.com/tutorials/incremental-data-synchronization#step-2). If you encounter any issues with the state after the update, you may need to troubleshoot based on the specific error messages or symptoms you observe. In some cases, reviewing the [schema change management documentation](https://docs.airbyte.com/using-airbyte/schema-change-management#resolving-breaking-changes) may also be helpful if the update involves breaking changes.