How to handle Redshift non-idempotency problem on data loading

As you probably know, in Redshift constraints (uniqueness, primary key, foreign key, not null) are informational only. This means that if you insert 2 times an entry in a table that has defined a primary key, that table will contain that entry 2 times. Now, let’s imagine the following scenario: your application follows the recommendations […]