Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1667386101.1240476647724.JavaMail.jira@brutus>
Date: Thu, 23 Apr 2009 01:50:47 -0700 (PDT)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Closed: (DERBY-4056) Space is not reclaimed when attempting
 to insert row that violates UNIQUE constraint
In-Reply-To: <578532343.1234520159660.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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.