[
https://issues.apache.org/jira/browse/DERBY-4152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-4152:
----------------------------------
Attachment: TestInPlaceCompressWithPKViolation.java
Well I thought maybe the changes to SYSCS_INPLACE_COMPRESS_TABLE might have
changed what gets reclaimed on inplace compress, but found that inplace
compress does not reclaim the space after primary key violations even with
10.4. The attached program shows the same number of allocated pages (913)
after inplace compress. SYSCS_COMPRESS_TABLE does reclaim the space and reduces
NUMALLOCATEDPAGES to 95 in both versions.
Tomorrow I'll see if I can get the PK violations out of the test and see if it
still grows.
> 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: 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.
