| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
| Cc: | "nikita(dot)y(dot)volkov(at)mail(dot)ru" <nikita(dot)y(dot)volkov(at)mail(dot)ru>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: BUG #12330: ACID is broken for unique constraints |
| Date: | 2014-12-26 15:50:41 |
| Message-ID: | 31635.1419609041@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Kevin Grittner <kgrittn(at)ymail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Egoitz Aurrekoetxea | 2014-12-26 16:07:35 | Re: BUG #12344: libcurses issue with psql binary of Solaris package |
| Previous Message | Bruce Momjian | 2014-12-26 15:47:12 | Re: BUG #12324: database's age less then max(relAGE) , and stream standby diff with master |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-12-26 15:52:58 | Re: What exactly is our CRC algorithm? |
| Previous Message | Bruce Momjian | 2014-12-26 15:50:33 | Re: What exactly is our CRC algorithm? |