Impacts On You #

1. Easier Updates : With a single deterministic primary key, that doesn't change from version to version. You can be confident that Source Plugin Updates won't require a schema change on your end.
2. CloudQuery Spec Configs: If you are using the AWS Plugin and have set the deterministic_cq_id: true and pk_mode: cq-id-only options then you will see no change in behavior. In this case you can remove those options from your spec and the plugin will continue to work as expected.
3. Adoption: If you are using the latest version (v7.3.1) of the Postgres Destination plugin it will handle all of the migrations for you. If you are using an older version of the Postgres Destination plugin or any other destination that support write modes other than append you will need to manually update your schema to remove the compound primary key and add the _cq_id field as the primary key. Users can set migrate_mode: true and CloudQuery will migrate the table by dropping the existing table and remaking the table with the improved schema.
4. Performance: We expect that for most destinations that support Primary Keys this change will have a negligible or small positive impact on sync times. ****Depending on your queries you might see an increase in latency if you were previously utilizing an index. In these cases you can manually add indexes to your data to improve performance.