Re: BUG #13723: "duplicate key" error occurs when update delete and insert the same row concurrently - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #13723: "duplicate key" error occurs when update delete and insert the same row concurrently
Date
Msg-id CAKFQuwaC1q6bDDoXS0eTTgMGJHV_ZWi483j53SgZtjw71OXpFg@mail.gmail.com
Whole thread Raw
In response to BUG #13723: "duplicate key" error occurs when update delete and insert the same row concurrently  (chjischj@163.com)
List pgsql-bugs
On Sunday, October 25, 2015, <chjischj@163.com> wrote:

> The following bug has been logged on the website:
>
> Bug reference:      13723
> Logged by:          ChenHuajun
> Email address:      chjischj@163.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.

pgsql-bugs by date:

Previous
From: chjischj@163.com
Date:
Subject: BUG #13723: "duplicate key" error occurs when update delete and insert the same row concurrently
Next
From: Tom Lane
Date:
Subject: Re: BUG #13723: "duplicate key" error occurs when update delete and insert the same row concurrently