What exactly did the change to BTree fix? We're still getting file growth in production, even when I've forced the locking mechanism to serialize (so it's most likely not a concurrency problem).
InfoTrust Group, Inc.
500 Discovery Parkway, Suite 200
Superior, CO 80027
This e-mail and all information included herein do not constitute a legal agreement accorded by INFOTRUST GROUP and its affiliates and subsidiaries. All legal agreements must be formulated in writing by a legal representative of INFOTRUST GROUP. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail by mistake, please inform us and destroy this e-mail and any documents it might contain. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. Thank you for your cooperation.
From: Wolfgang Meier <wolfgang@ex...> - 2010-06-30 13:54:15
> What exactly did the change to BTree fix? We're still getting file growth
> in production, even when I've forced the locking mechanism to serialize (so
> it's most likely not a concurrency problem).
The fix addresses a serious backup/restore issue which was reported
off-list. It effectively leads to parts of your data not being found
and is thus an important issue which got highest priority, even if
only a few users seem to have recognized it.
It has nothing to do with the dom.dbx file growth you experienced. The
possible causes of this file growth are still a bit mysterious to me.
Get latest updates about Open Source Projects, Conferences and News.