Hi, I am working on extracting PostgresSQL CDC data using Airbyte and importing it into Snowflake. The main challenge I face is "Schema Drift" that was not supported by the Postgres connector any how. Unfortunately, any schema changes would not be reflected in the target database and the pipeline breaks now or later stage. Moreover, I am bit un-reliable on the communication from Operational systems for any schema drift. Have you ever dealt with such challenges? How did you ensure schema changes are communicated earlier ? or Atleast know to you before the pipeline breaks? I am drafting operational procedure at the moment but I am not optimistic on this part. Any schema validator you have written? Any use case would give me some thoughts to deal this situation. Thank you for your understanding and support.

Hmm, I don't know enough to give you a confident answer yet. The information extracts provided do not contain specific details on handling schema drift with Airbyte when extracting data from PostgreSQL and importing it into Snowflake. However, I can suggest that you check out the [Airbyte documentation](https://docs.airbyte.com) or join the conversation on [Airbyte’s community Slack Channel](https://airbyte.io/community) or [Airbyte’s discourse](https://discuss.airbyte.io/) for more specific guidance on this topic.