For a usecase, I am evaluating the postgres connector for extracting cdc events using Postgres logical replication. It seems the schema drift (adding a column) is manual process. On adding a new column, the schema needs to be refreshed and reset needs to be done that deletes the data on target. Upon sync all rows are added once again with updated schema. I would like to know if airbyte can handle schema drift (add a new column) without schema refresh and data reset.

Based on the information provided in the extracts, Airbyte does not currently support automatic handling of schema changes for CDC sources. If you make a schema change, such as adding a new column, you will need to manually reset and resync the data. This is because schema changes are not automatically supported for CDC sources in Postgres [source](https://docs.airbyte.com/integrations/sources/postgres/postgres-troubleshooting). However, Airbyte does provide a feature to detect and propagate schema changes. You can specify for each connection how Airbyte should handle any change of schema in the source. Airbyte checks for any changes in your source schema before syncing, at most once every 24 hours. Based on your configured settings for "Detect and propagate schema changes", Airbyte can automatically sync those changes or ignore them. The options include: - Propagate all changes - Propagate column changes only - Ignore any schema change - Pause connection When a new column is detected and propagated, values for that column will be filled in for the updated rows. If you are missing values for rows not updated, a backfill can be done by completing a full refresh [source](https://docs.airbyte.com/cloud/managing-airbyte-cloud/manage-schema-changes/). In conclusion, while Airbyte does provide some level of automation in handling schema changes, it does not currently support automatic handling of schema changes without a schema refresh and data reset for CDC sources.