| From: | Marko Tiikkaja <marko(at)joh(dot)to> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)ymail(dot)com>, "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:44:25 |
| Message-ID: | 549D8259.3090109@joh.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next 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 |
| Previous Message | Tom Lane | 2014-12-26 15:41:23 | Re: BUG #12330: ACID is broken for unique constraints |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2014-12-26 15:50:33 | Re: What exactly is our CRC algorithm? |
| Previous Message | Tom Lane | 2014-12-26 15:41:23 | Re: BUG #12330: ACID is broken for unique constraints |