[DERBY-4056] Space is not reclaimed when attempting to insert row that violates UNIQUE constraint

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 10.4.2.0, 10.5.1.1
• Component/s: Store
• Assignee: Unassigned
• Reporter: Knut Anders Hatlen
• Created: 13/Feb/09 10:15
• Updated: 27/Jul/11 19:57
• Resolved: 23/Apr/09 08:50

Description

If you try to insert a row which would violate a unique constraint,
the insert is rolled back, but the space is not reclaimed.

This was mentioned in a comment to DERBY-4028 (26/Jan/09):

> Out of curiosity, I tried this code:
>
> s.execute("create table d4028(x int unique)");
> while (true) {
> try

{ > s.execute("insert into d4028 values 1"); > }

catch (SQLException e)

{ > System.out.println(e); > }

> }
>
> Even though it only inserts one row, the disk footprint just keeps
> growing. It's the disk footprint of the table that's growing, though,
> not the index, so it looks like the free space in the index is reused.

Issue Links

• duplicates: DERBY-691 committed deleted row space reclamation may be missed if delete is actually an aborted insert.
• is related to: DERBY-4050 Multithreaded clob update causes growth in table that does not get reclaimed
• is related to: DERBY-4057 Space is not reclaimed if transaction is rolled back
• is related to: DERBY-5356 Tracking for Derby space reclamation issues