Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id BB8E863290B for ; Thu, 25 Mar 2010 17:38:20 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 75040-09 for ; Thu, 25 Mar 2010 20:38:10 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-pw0-f46.google.com (mail-pw0-f46.google.com [209.85.160.46]) by mail.postgresql.org (Postfix) with ESMTP id 33C70631B0A for ; Thu, 25 Mar 2010 17:38:09 -0300 (ADT) Received: by pwi5 with SMTP id 5so4528759pwi.19 for ; Thu, 25 Mar 2010 13:38:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=VB3XCn7Pna/CqZ57tDa5XXkmefDmuLVB1FVQ9XiQMPo=; b=G3/6B86UrekibPbxvcQV0krIh0fUO5yWHELV5KCIEHRqk4eHaIdpAytOVlsqjM+1+S aShiuRtgQ7vS8sHG1r1lUHKn3sfnjJ2AgklS4tWtC7OkSJnSBfsTcww0LDxSYutIhtUP iLnnYo1TtgsE763WuIjAQyUZEIzLH0y2r25fc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=mOiyxaQyiv1QmI8pSPGBOf0Q6M7OaapntoWkAbb36k9BwGz1Rj9HvgL4bKX1foenjd dAlQvp1Ch3t2hlvAOq2PouWBRphelnMOItuWXysZnJrLrJ5Icak5hKm1fU/QCiETlMHI VH9RhZGTW5EeRHEZ2yx4rS6dIUS4VIYoF7zRk= MIME-Version: 1.0 Received: by 10.140.247.17 with SMTP id u17mr628279rvh.151.1269549488024; Thu, 25 Mar 2010 13:38:08 -0700 (PDT) In-Reply-To: References: <4BA23936.2030507@gmail.com> <4BA596D2.4050406@squeakycode.net> <20100323185232.GD6662@rice.edu> <5342.1269372121@sss.pgh.pa.us> <4BA934B9.9070401@2ndquadrant.com> <4BA9D39B.6020103@gmail.com> <1269421198.11473.50.camel@hvost> <4BABC1E0.7010607@mansionfamily.plus.com> Date: Thu, 25 Mar 2010 14:38:07 -0600 Message-ID: Subject: Re: mysql to postgresql, performance questions From: Scott Marlowe To: Pierre C Cc: James Mansion , Hannu Krosing , Yeb Havinga , Greg Smith , Tom Lane , "Ross J. Reedstrom" , pgsql-performance@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.26 tagged_above=-10 required=5 tests=BAYES_20=-0.74, SARE_OEM_OBFU=1 X-Spam-Level: X-Archive-Number: 201003/327 X-Sequence-Number: 38152 On Thu, Mar 25, 2010 at 2:29 PM, Pierre C wrote: >> Hannu Krosing wrote: >>> >>> Pulling the plug should not corrupt a postgreSQL database, unless it was >>> using disks which lie about write caching. >>> >> Didn't we recently put the old wife's 'the disks lied' tale to bed in >> favour of actually admiting that some well known filesystems and saftware >> raid systems have had trouble with their write barriers? > > I put a cheap UPS on the home server (which uses Software RAID) precisely > because I don't really trust that stuff, and there is also the RAID5 write > hole... and maybe the RAID1 write hole too... and installing a UPS takes > less time that actually figuring out if the system is power-loss-safe. Very true, a UPS might not cover every possible failure mode, but it sure takes care of an aweful lot of the common ones.