Hi Team, My postgres source tables have primary key but still increment deduped sync option is not available. According to document it should be there. Can someone help me on this.

What destination connector are you using? Some destination doesn’t allow dedup+history mode.

Hi @Marcos Marx (Airbyte), I am using destination S3. However dedup+history is depend on source connector right? Because I am using postgres source which has cursor and primary key.

No, it depends from destination not Source. Only sources with dbt module has dedup+history

Okay, If I want to achieve dedup+history with postgres source and S3 destination what should I do?

No, it isn’t possible.

Using CDC for postgres can I achieve it?

The dedup+history has dependency from the destination and not the source. Only destination with dbt module has support to it.

Can you provide any resource for S3 destination with dbt?

@Rahul Borse not all destination support dedup+history, S3 is one of them. dbt doesn’t have a module for S3.