Issue Details (XML | Word | Printable)

Key: CORE-4382
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Dimitry Sibiryakov
Reporter: Dimitry Sibiryakov
Votes: 0
Watchers: 2
Operations

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

User savepoints are not released on commit

Created: 04/Apr/14 12:59 PM   Updated: 23/Sep/15 11:21 AM
Component/s: Engine
Affects Version/s: 2.5.0, 2.5.1, 2.5.2, 2.1.5 Update 1, 2.5.2 Update 1, 3.0 Alpha 1, 3.0 Alpha 2, 2.1.6, 2.5.3, 3.0 Beta 1, 2.1.7, 2.5.3 Update 1
Fix Version/s: 2.5.4, 3.0 Beta 2

File Attachments: 1. File tra.diff (0.8 kB)


QA Status: Done successfully
Test Details:
Confirmed result of "gstat -i"
1) for 3.0 Alpha1 & Alpha2:
Root page: 203, depth: 1, leaf buckets: 1, nodes: 6 // i.e. 6 orphans instead of expected 1

2) for 2.5.3:
Depth: 1, leaf buckets: 1, nodes: 6 // i.e. 6 orphans instead of expected 1


 Description  « Hide
Following script leaves in index several orphan nodes.

create database "g_test";
create table g_test (f integer);
create index g_ind on g_test (f);
insert into g_test values (1);
commit;
update g_test set f=2;
savepoint a;
update g_test set f=3;
savepoint b;
update g_test set f=4;
savepoint c;
update g_test set f=5;
savepoint d;
update g_test set f=6;
savepoint e;
update g_test set f=7;
commit;
select * from g_test;

Proposed patch is attached

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