David Fetter wrote: > The DEFERRED uniqueness constraints in 8.5alpha3 fix this problem That fix has a drawback: when the unique constraint is violated, the rest of the transaction runs with data that is somehow corrupted, with duplicate values being visible. It may be uneasy to predict if and how the statements following the temporary-ignored constraint violation will misbehave. Generally, the transaction will ultimately fail and the mess will be cleaned up by the rollback, but in the worst case it may not even fail, for instance if the offending rows get deleted before the end. Best regards, -- Daniel PostgreSQL-powered mail user agent and storage: http://www.manitou-mail.org -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
