Re: fsync = true beneficial on ext3? - Mailing list pgsql-general

From scott.marlowe
Subject Re: fsync = true beneficial on ext3?
Date
Msg-id Pine.LNX.4.33.0402100918210.28531-100000@css120.ihs.com
Whole thread Raw
In response to Re: fsync = true beneficial on ext3?  (JM <jerome@gmanmi.tv>)
List pgsql-general
Yep, it does.  We use the lsi megaraid in our postgresql box with and it
has passed all the power plug pull tests we've thrown at it.

On Tue, 10 Feb 2004, JM wrote:

> Would a battery backed Card do the trick?
>
>
>
>
> On Tuesday 10 February 2004 00:42, Bruce Momjian wrote:
> > 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?
> >
> > Yes, it does.  Without fsync, you can't be sure the data has been pushed
> > to the disk drive in case of an OS crash or power failure.
> >
> > > 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?
> >
> > The fsync makes sure it hits the drive, rather than staying in the
> > kernel cache during an OS failure.
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>


pgsql-general by date:

Previous
From: "scott.marlowe"
Date:
Subject: Re: I want to use postresql for this app, but...
Next
From: "scott.marlowe"
Date:
Subject: Re: number of rows in a cursor