On 2014-12-26 17:23, Kevin Grittner wrote:
Are there any objections to generating a write conflict instead of a duplicate key error if the duplicate key was added by a concurrent transaction? Only for transactions at isolation level REPEATABLE READ or higher?
Is it possible to distinguish between an actual write conflict and a completely unrelated UNIQUE constraint ending up violated for some reason?
.marko -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers