Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed attempt to violate unique constraint could leave unneeded "lock conflict" error in status-vector [CORE3394] #3760

Closed
firebird-automations opened this issue Mar 17, 2011 · 4 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @hvlad

This is bad, as it have unneeded error in status-vector :

DDL: CREATE TABLE T1 (ID INT)
DDL: CREATE UNIQUE INDEX T1_UQ ON T1 (ID)
DDL: COMMIT

tx1: SET TRANSACTION READ COMMITTED RECORD_VERSION NO WAIT
tx1: INSERT INTO T1 VALUES (1)
tx2: SET TRANSACTION READ COMMITTED RECORD_VERSION NO WAIT
tx2: INSERT INTO T1 VALUES (1)
lock conflict on no wait transaction
attempt to store duplicate value (visible to active transactions) in unique index "T1_UQ"

More, if someone tried to catch isc_no_dup and handle it in some way he well be in trouble.

Commits: 09b756b 6cdb30e f8c6908

====== Test Details ======

Confirmed on WI-V2.5.0.26074, STDERR was:
Statement failed, SQLSTATE = 40001
lock conflict on no wait transaction -- <<< !!! <<<
-violation of PRIMARY or UNIQUE KEY constraint "T_PK" on table "T"

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

assignee: Vlad Khorsun [ hvlad ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.5.1 [ 10333 ]

Fix Version: 3.0 Alpha 1 [ 10331 ]

Fix Version: 2.1.5 [ 10420 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: Done successfully

Test Details: Confirmed on WI-V2.5.0.26074, STDERR was:
Statement failed, SQLSTATE = 40001
lock conflict on no wait transaction -- <<< !!! <<<
-violation of PRIMARY or UNIQUE KEY constraint "T_PK" on table "T"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment