Re: turning fsync off for WAL - Mailing list pgsql-general

From Scott Marlowe
Subject Re: turning fsync off for WAL
Date
Msg-id dcc563d10806021738u1086645eo48e63522d634bdd@mail.gmail.com
Whole thread Raw
In response to turning fsync off for WAL  ("Ram Ravichandran" <ramkaka@gmail.com>)
Responses Re: turning fsync off for WAL  ("Ram Ravichandran" <ramkaka@gmail.com>)
List pgsql-general
On Mon, Jun 2, 2008 at 6:12 PM, Ram Ravichandran <ramkaka@gmail.com> wrote:
> Hey,
> I am running a postgresql server on Amazon EC2. My current plan is to mount
> an Amazon S3 bucket as a drive using PersistentFS which is a POSIX-compliant
> file system.
> I will be using this for write-ahead-logging. The issue with S3 is that
> though the actual storage is cheap, they charge $1 per 100,000 put requests
>  - so frequent fsyncs will
> cost me a lot.
> I've been talking to the makers of persistentFS, and one possible solution
> is for the file system to disobey fsyncs. I am trying to find out the
> implications of this method in
> case of a crash. Will I only lose information since the last fsync? Or will
> the earlier data, in general, be corrupted due to some out-of-order writes
> (I remember seeing this somewhere)?

Running without fsyncs is likely to lead to a corrupted db if you get
a crash / loss of connection etc...

pgsql-general by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Maintaining an index on a large table: Is there any potential for it to stall my application?
Next
From: "Ram Ravichandran"
Date:
Subject: Re: turning fsync off for WAL