Re: Final(?) proposal for wal_sync_method changes

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Final(?) proposal for wal_sync_method changes
Date: 2010-12-07 23:21:50
Message-ID: 4CFEC18E.9050204@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12/07/2010 06:11 PM, Tom Lane wrote:
> Josh Berkus<josh(at)agliodbs(dot)com> writes:
>> On 12/7/10 2:28 PM, Tom Lane wrote:
>>> Another point here is that it's not clear why we're selecting a
>>> known-to-be-insecure default on OS X (where in fact all methods except
>>> fsync_writethrough fail to push data to disk). We've been around on
>>> that before, of course, and maybe now is not the time to change it.
>> Because nobody sane uses OSX on the server?
> Some of us would make the same remark about Windows. But we go out of
> our way to provide a safe default on that platform anyhow.
>
>

In practice, though, Windows is used a lot on servers and OSX isn't.
That means we are probably going to have lots less push on this sort of
thing from the OSX community, which is not to say that we shouldn't try
to be just as safe on OSX as we try to be everywhere else.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2010-12-07 23:22:52 Re: Final(?) proposal for wal_sync_method changes
Previous Message Tom Lane 2010-12-07 23:11:22 Re: Final(?) proposal for wal_sync_method changes