From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by yquem.inria.fr (Postfix) with ESMTP id ED9B5BB81 for ; Fri, 18 Nov 2005 21:01:58 +0100 (CET) Received: from pauillac.inria.fr (pauillac.inria.fr [128.93.11.35]) by nez-perce.inria.fr (8.13.0/8.13.0) with ESMTP id jAIK1w9o015321 for ; Fri, 18 Nov 2005 21:01:58 +0100 Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id VAA23191 for ; Fri, 18 Nov 2005 21:01:57 +0100 (MET) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.173]) by nez-perce.inria.fr (8.13.0/8.13.0) with ESMTP id jAIK1v0q015316 for ; Fri, 18 Nov 2005 21:01:57 +0100 Received: from [212.227.126.160] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1EdCQi-0004Ow-00; Fri, 18 Nov 2005 21:01:52 +0100 Received: from [84.58.96.79] (helo=gate.lan.gerd-stolpmann.de) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 1EdCQi-0004yp-00; Fri, 18 Nov 2005 21:01:52 +0100 Received: from flakew.lan.gerd-stolpmann.de (flakew.lan.gerd-stolpmann.de [192.168.0.32]) by gate.lan.gerd-stolpmann.de (Postfix) with ESMTP id 24F7AC097; Fri, 18 Nov 2005 21:01:52 +0100 (CET) Subject: Re: [Caml-list] [1/2 OT] Indexing (and mergeable Index-algorithms) From: Gerd Stolpmann To: Florian Weimer Cc: Thomas Fischbacher , Oliver Bandel , caml-list@inria.fr In-Reply-To: <87hdaayolx.fsf@mid.deneb.enyo.de> References: <20051116234238.GA5741@first.in-berlin.de> <87r79fjxy4.fsf@mid.deneb.enyo.de> <1132325649.17170.1.camel@starlight> <20051118142244.GF1116@first.in-berlin.de> <87wtj6yqbw.fsf@mid.deneb.enyo.de> <87hdaayolx.fsf@mid.deneb.enyo.de> Content-Type: text/plain Date: Fri, 18 Nov 2005 21:01:51 +0100 Message-Id: <1132344112.17483.9.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 Content-Transfer-Encoding: 7bit X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:a6865a839c0178d9aa0ce41878507ea2 X-Miltered: at nez-perce with ID 437E3336.001 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Miltered: at nez-perce with ID 437E3335.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Spam: no; 0.00; caml-list:01 indexing:01 gerd:01 stolpmann:01 gerd:01 stolpmann:01 viktoriastr:01 64293:01 darmstadt:01 data:02 florian:02 telefon:02 berkeley:03 berkeley:03 crashes:03 X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.0.3 Am Freitag, den 18.11.2005, 16:14 +0100 schrieb Florian Weimer: > * Thomas Fischbacher: > > >> No, it isn't. Berkeley DB offers much richer functionality, including > >> transactions and replication. > > > > However, crashes at unfortunate moments may lead to database > > corruption, > > All my crashes could be traced back to operator error and faulty > hardware. Berkeley DB has a very bad reputation when it comes to data > integrity and durability, but in my experience, this is simply not > true. I think it is true. A good database must not become corrupt even if the hardware crashes. It must be possible to simply undo the last operation after a crash, and the integrity must not suffer from that. Although BDB promises this stability, I had to throw away a number of databases after hardware crashes. There are simply errors in it, and I cannot recommend it anymore. Gerd -- ------------------------------------------------------------ Gerd Stolpmann * Viktoriastr. 45 * 64293 Darmstadt * Germany gerd@gerd-stolpmann.de http://www.gerd-stolpmann.de Telefon: 06151/153855 Telefax: 06151/997714 ------------------------------------------------------------