From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
---|---|
To: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: fsync = true beneficial on ext3? |
Date: | 2004-02-09 17:19:15 |
Message-ID: | Pine.LNX.4.33.0402091018090.24217-100000@css120.ihs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, 8 Feb 2004, Ed L. wrote:
>
> I'm curious what the consensus is, if any, on use of fsync on ext3
> filesystems with postgresql 7.3.4 or later. I did some recent performance
> tests demonstrating a 45%-70% performance improvement for simple inserts
> with fsync off on one particular system. Does fsync = true buy me any
> additional recoverability beyond ext3's journal recovery?
>
> If we write something without sync'ing, presumably it's immediately
> journaled? So even if the DB crashes prior to fsync'ing, are we fully
> recoverable? I've been running a few pgsql clusters on ext3 with fsync =
> false, suffered numerous OS crashes, and have yet to lose any data or see
> any corruption from any of those crashes. Have I just been lucky?
With all the other posts on this topic, I just want to point out that it's
all theory until you build your machine, set it up, initiate a hundred or
so parallel transactions, and pull the plug in the middle.
Without pulling the plug, you just don't know for sure. And you need to
do it a few times, in case your machine "got lucky" once and might fail on
subsequent power fails.
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Rawnsley | 2004-02-09 17:25:52 | Re: Oracle SQLNet on same server as Postgres |
Previous Message | Lincoln Yeoh | 2004-02-09 17:18:43 | Re: Quad Xeon vs. Dual Itanium |