pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <scott.marlowe@gmail.com>
To: James Mansion <james@mansionfamily.plus.com>
Cc: Hannu Krosing <hannu@2ndquadrant.com>
Cc: Yeb Havinga <yebhavinga@gmail.com>
Cc: Greg Smith <greg@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Ross J. Reedstrom <reedstrm@rice.edu>
Cc: pgsql-performance@postgresql.org
Subject: Re: mysql to postgresql, performance questions
Date: Thu, 25 Mar 2010 14:24:04 -0600
Message-ID: <dcc563d11003251324t82e7c10ga607142a0a111028@mail.gmail.com> (raw)
In-Reply-To: <4BABC1E0.7010607@mansionfamily.plus.com>
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>

On Thu, Mar 25, 2010 at 2:04 PM, James Mansion
<james@mansionfamily.plus.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 believe so.  It was determined to be a combination of several
culprits, and only a few hard drives from back in the day apparently
ever had this problem.

Of course now it seems that modern SSDs may lie about cache if they
don't have a big enough capacitor to guarantee they can write out
their internal cache etc.

The sad fact remains that many desktop / workstation systems lie, and
quite a few servers as well, for whatever reason.



view thread (44+ messages)  latest in thread

Message-ID: <dcc563d11003251324t82e7c10ga607142a0a111028@mail.gmail.com>
Permalink:  ../dcc563d11003251324t82e7c10ga607142a0a111028@mail.gmail.com/
Also on:    postgresql.org/message-id/dcc563d11003251324t82e7c10ga607142a0a111028@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: scott.marlowe@gmail.com, james@mansionfamily.plus.com, hannu@2ndquadrant.com, yebhavinga@gmail.com, greg@2ndquadrant.com, tgl@sss.pgh.pa.us, reedstrm@rice.edu
  Subject: Re: mysql to postgresql, performance questions
  In-Reply-To: <dcc563d11003251324t82e7c10ga607142a0a111028@mail.gmail.com>
  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> <dcc563d11003251324t82e7c10ga607142a0a111028@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox