Issue Details (XML | Word | Printable)

Key: CORE-2988
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
Assignee: Nickolay Samofatov
Reporter: Nickolay Samofatov
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Firebird Core

Concurrent transaction number not reported if lock timeout occurs

Created: 04/May/10 05:28 PM   Updated: 28/May/15 05:08 PM
Component/s: None
Affects Version/s: 2.1.3, 2.5 RC2
Fix Version/s: 3.0 Alpha 1

Issue Links:
Duplicate
 

QA Status: Done successfully


 Description  « Hide
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;

          ID
============
Statement failed, SQLCODE = -901
lock time-out on wait transaction


 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.