I have posted the issue to DERBY-5487. I have also attached the Java test program.
The test rows do insert at one end of the primary key and delete the other end.. Interestingly, I noticed that primary key space is reclaimed if I reuse the primary keys across the insert-delete loops. But, my application requires me to use continuously increasing primary keys (not reuse them). Mike Matrigali wrote: > > Posting your test to a JIRA issue would be best. It would be > interesting to post the space table results after each > insert/delete/compress iteration (or every 10, ...). > When do you commit (every row or every 10000)? Is it multi-threaded? > Does your > test always insert rows at one end of the index and delete them > from the other end. If so it may be DERBY-5473 (a runtime issue, > not a compress table issue). > > -- View this message in context: http://old.nabble.com/SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE-question-tp32736560p32742387.html Sent from the Apache Derby Users mailing list archive at Nabble.com.
