[
https://issues.apache.org/jira/browse/DERBY-4056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen closed DERBY-4056.
-------------------------------------
Resolution: Duplicate
This is a duplicate of DERBY-691. Closing as such.
> Space is not reclaimed when attempting to insert row that violates UNIQUE
> constraint
> ------------------------------------------------------------------------------------
>
> Key: DERBY-4056
> URL: https://issues.apache.org/jira/browse/DERBY-4056
> Project: Derby
> Issue Type: Bug
> Components: Store
> Affects Versions: 10.4.2.0, 10.5.0.0
> Reporter: Knut Anders Hatlen
> Attachments: InsertDuplicateKey.java
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
