We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Submitted by: @samofatov
Assigned to: @samofatov
Is duplicated by CORE4193
Firebird 2.1 added a feature to report concurrent transaction number when there is lock contention.
However, concurrent transaction number is not reported in two important cases, which severely limits its usefulness:
Lock timeouts during read operations:
create table test (id integer); insert into test values(1); commit;
ISQL1: set transaction read committed no record_version lock timeout 10; update test set id = id;
ISQL2: set transaction read committed no record_version lock timeout 10; select * from test;
ID
============ Statement failed, SQLCODE = -901 lock time-out on wait transaction -deadlock
Lock timeouts during pessimistic locking:
ISQL1: set transaction read committed lock timeout 10; select * from test with lock;
ISQL2: set transaction read committed lock timeout 10; select * from test with lock;
============ Statement failed, SQLCODE = -901 lock time-out on wait transaction
Commits: c84d62d
The text was updated successfully, but these errors were encountered:
assignee: Nickolay Samofatov [ skidder ]
Sorry, something went wrong.
status: Open [ 1 ] => Resolved [ 5 ]
resolution: Fixed [ 1 ]
Fix Version: 3.0 Alpha 1 [ 10331 ]
status: Resolved [ 5 ] => Closed [ 6 ]
Link: This issue block progress on CORE4193 [ CORE4193 ]
Link: This issue is duplicated by CORE4193 [ CORE4193 ]
Link: This issue block progress on CORE4193 [ CORE4193 ] =>
status: Closed [ 6 ] => Closed [ 6 ]
QA Status: Done successfully
No branches or pull requests
Submitted by: @samofatov
Assigned to: @samofatov
Is duplicated by CORE4193
Firebird 2.1 added a feature to report concurrent transaction number when there is lock contention.
However, concurrent transaction number is not reported in two important cases, which severely limits its usefulness:
Lock timeouts during read operations:
create table test (id integer);
insert into test values(1);
commit;
ISQL1:
set transaction read committed no record_version lock timeout 10;
update test set id = id;
ISQL2:
set transaction read committed no record_version lock timeout 10;
select * from test;
============
Statement failed, SQLCODE = -901
lock time-out on wait transaction
-deadlock
Lock timeouts during pessimistic locking:
ISQL1:
set transaction read committed lock timeout 10;
select * from test with lock;
ISQL2:
set transaction read committed lock timeout 10;
select * from test with lock;
============
Statement failed, SQLCODE = -901
lock time-out on wait transaction
Commits: c84d62d
The text was updated successfully, but these errors were encountered: