Skip site navigation (1) Skip section navigation (2)

Re: mysql to postgresql, performance questions

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Pierre C <lists(at)peufeu(dot)com>
Cc: James Mansion <james(at)mansionfamily(dot)plus(dot)com>, Hannu Krosing <hannu(at)2ndquadrant(dot)com>, Yeb Havinga <yebhavinga(at)gmail(dot)com>, Greg Smith <greg(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>, pgsql-performance(at)postgresql(dot)org
Subject: Re: mysql to postgresql, performance questions
Date: 2010-03-25 20:38:07
Message-ID: dcc563d11003251338m1369b4efh2efa600c9c8fe7dd@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
On Thu, Mar 25, 2010 at 2:29 PM, Pierre C <lists(at)peufeu(dot)com> 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.

In response to

Responses

pgsql-performance by date

Next:From: Yeb HavingaDate: 2010-03-25 21:22:08
Subject: Re: mysql to postgresql, performance questions
Previous:From: Pierre CDate: 2010-03-25 20:29:44
Subject: Re: mysql to postgresql, performance questions

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group