| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "chjischj(at)163(dot)com" <chjischj(at)163(dot)com> |
| Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #13723: "duplicate key" error occurs when update delete and insert the same row concurrently |
| Date: | 2015-10-25 14:27:03 |
| Message-ID: | CAKFQuwaC1q6bDDoXS0eTTgMGJHV_ZWi483j53SgZtjw71OXpFg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sunday, October 25, 2015, <chjischj(at)163(dot)com> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 13723
> Logged by: ChenHuajun
> Email address: chjischj(at)163(dot)com <javascript:;>
> PostgreSQL version: 9.4.5
> Operating system: CentOS 6
> Description:
>
> When i run sysbench's complex test with PostgreSQL, the following error
> always occured.
> duplicate key value violates unique constraint "%s"
>
> It seems to be a bug which occurs when executing update,delete and
> insert(within one transaction) the same row concurrently.
>
>
While I probably cannot explain this adequately it is your understanding of
concurrency and the various transaction isolation levels that is wrong; not
PostgreSQL.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-10-25 15:38:23 | Re: BUG #13723: "duplicate key" error occurs when update delete and insert the same row concurrently |
| Previous Message | chjischj | 2015-10-25 11:01:36 | BUG #13723: "duplicate key" error occurs when update delete and insert the same row concurrently |