On Mon, Nov 11, 2024 at 12:41 AM yudhi s <learnerdatabas...@gmail.com> wrote: > So it means it will ensure no duplication happens for ID values, but still we > are seeing "duplicate key" error. So what is the possible reason here or are > we encountering any buggy behaviour here?
MERGE doesn't actually make any promises about not getting unique violations. Only ON CONFLICT DO UPDATE (and ON CONFLICT DO NOTHING) make such a promise. That's the main reason why Postgres supports both. -- Peter Geoghegan
