From owner-freebsd-hackers@FreeBSD.ORG Tue May 13 20:48:35 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 17FB91065670 for ; Tue, 13 May 2008 20:48:35 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: from mired.org (five.mired.org [66.92.153.75]) by mx1.freebsd.org (Postfix) with ESMTP id AFC0E8FC2B for ; Tue, 13 May 2008 20:48:34 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 18044 invoked by uid 1001); 13 May 2008 16:49:01 -0400 Received: from bhuda.mired.org (bhuda [192.168.195.1]) by bhuda (tmda-ofmipd) with ESMTP; Tue, 13 May 2008 16:49:00 -0400 Date: Tue, 13 May 2008 16:49:00 -0400 To: Anthony Pankov Message-ID: <20080513164900.35f89e47@bhuda.mired.org> In-Reply-To: <2117635718.20080513154406@mail.ru> References: <9FC19AC2-DAD8-418C-8B9C-F129DEC58CEF@gmail.com> <15336578.20080512123806@mail.ru> <200805121153.00809.jonathan+freebsd-hackers@hst.org.za> <1663320218.20080512223531@mail.ru> <20080512152430.3720683e@mbook.local> <2117635718.20080513154406@mail.ru> Organization: Meyer Consulting X-Mailer: Claws Mail 3.4.0 (GTK+ 2.12.9; amd64-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Delivery-Agent: TMDA/1.1.12 (Macallan) From: Mike Meyer Cc: freebsd-hackers@freebsd.org Subject: Re: BDB corrupt X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 20:48:35 -0000 On Tue, 13 May 2008 15:44:06 +0400 Anthony Pankov wrote: > > Monday, Mike Meyer May 12, 2008, 11:24:30 PM, you wrote: > > MM> On Mon, 12 May 2008 22:35:31 +0400 Anthony Pankov wrote: > >> Because BDB: > >> 1. do not need additional installation > >> 2. is part of base system which mean it is mature, reliable and stable > > MM> BDB in the base system is mature, reliable and stable *for what it's > MM> used for in the base system.* So long as your requirements are covered > MM> by that usage, you'll be ok. > > MM> The uses I know of for BDB in the base system all consist of databases > MM> of relatively small items that are changed infrequently, and usually > MM> with a locking mechanism. From what you've said, this doesn't describe > MM> your requirements. > > MM> More importantly, from what other people are saying, your requirements > MM> are ones for which it's known that BDB is *not* reliable, or otherwise > MM> unsuitable. In particular, an effort is underway to allow parallel > MM> ports builds, which implies concurrent access to the database, which > MM> is a known source of problems for BDB. > > MM> > My requirements is > 1. there is no need for SQL > 2. processes are sharing db file in concurrent mode > 3. reading/writing = 60%/40% > > With BDB > clause 1 - satisfied > clause 3 - satisfied (databases of relatively small items that are > changed infrequently). Actually, I don't think you get #3, because my wording was poor. The things in the base system are databases of small items, where the *database* is changed infrequently. I think what you have is a database of small items where the *items* are changed infrequently, but the database itself changes frequently. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. O< ascii ribbon campaign - stop html mail - www.asciiribbon.org