Re: BUG #12330: ACID is broken for unique constraints - Mailing list pgsql-hackers

From Tom Lane
Subject Re: BUG #12330: ACID is broken for unique constraints
Date
Msg-id 31635.1419609041@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #12330: ACID is broken for unique constraints  (Kevin Grittner <kgrittn@ymail.com>)
Responses Re: BUG #12330: ACID is broken for unique constraints  (Kevin Grittner <kgrittn@ymail.com>)
List pgsql-hackers
Kevin Grittner <kgrittn@ymail.com> writes:
> 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?

Yes.  This will deliver a less meaningful error code, *and* break
existing code that is expecting the current behavior.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: What exactly is our CRC algorithm?
Next
From: Andres Freund
Date:
Subject: Re: What exactly is our CRC algorithm?