Hi Airbyte, I have an concern around mismatches in data where tables related to foreign key constraints and triggers during the refresh process using airbyte for postgres to postgres migration. Since Airbyte does not guarantee parent tables are loaded before child tables, keeping foreign keys enabled could result in constraint violations during data loads. Similarly, if triggers remain enabled, they may fire during bulk refresh operations and introduce additional or unintended data changes, which could lead to discrepancies between source and target. Because of these limitations, disabling foreign keys and triggers during the refresh helps ensure a clean and consistent load, and they can be re-enabled once the refresh completes. Do you have any idea how to disable these and re-enable these in target when needed (both FK and Triggers ) or some how airbyte handles these issue internal can anyone clarify

Airbyte doesn't touch foreign keys or triggers. That would be up to the user. The bulk load should happen only once, and then all subsequent syncs will be incremental. Is there a reason you're not using native Postgres replication?