[
https://issues.apache.org/jira/browse/DERBY-4152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-4152:
----------------------------------
The initial behavior you report for inplace space compress and pk violation
does seem like a bug. I was expecting all pages to be marked as free that were
associcated with the clob/blob that were aborted as part of the pk violation.
It is known this does not happen at abort time but was expecting inplace
compress to get it back at least as free pages.
The only thing I am wondering about is that there may be multiple layers of
post commit actions and timing involved. the inplace compress searches the
head pages for deleted rows and purges these. These purges I belive in term
queue post commit actions to free the underlying long column chains, which will
take place in background.
I am going to run some tests to see if this is happening.
> mailjdbc test database grows very fast with 10.5
> -------------------------------------------------
>
> Key: DERBY-4152
> URL: https://issues.apache.org/jira/browse/DERBY-4152
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.5.1.0
> Environment: java version "1.6.0"
> Java(TM) SE Runtime Environment (build pwi3260sr3-20081106_07(SR3))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Windows 2000 x86-32
> jvmwi3260-200811
> 05_25433 (JIT enabled, AOT enabled)
> J9VM - 20081105_025433_lHdSMr
> JIT - r9_20081031_1330
> GC - 20081027_AB)
> Windows 2000 5.00.2195 /Service pack 4
> 4 CPU 3.00GHz
> Reporter: Kathey Marsden
> Priority: Critical
> Attachments: derby-4152_quick_change_to_stop_pk_violation_diff.txt,
> insertMailSummary.txt, TestInPlaceCompressWithPKViolation.java,
> TestInPlaceCompressWithPKViolation.java
>
>
> When I ran the mailjdbc test on 10.5.1.0 RC I found that the mailsdb database
> grew to 16GB after two days. On 10.4.2.0 on the same machine with the same
> configuration (no derby.properties) it grew to only 1.7GB after 7 days. Both
> were sane builds.
> This is with the embedded configuration:
> java org.apache.derbyTesting.system.mailjdbc.MailJdbc embedded
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
