>And it's not "silently corrupting" things - it's logging the conflicts to postgresql's log and, if configured, to a historical table. I stand corrected. Still

>And it's not "silently corrupting" things - it's logging the conflicts to postgresql's log and, if configured, to a historical table. I stand corrected. Still, it would be useful if there was a mode when it blew up because that would make sure the data is always consistent even if the application forgets to check the historical table.