Re: Simplifying wal_sync_method - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Simplifying wal_sync_method
Date
Msg-id 18587.1123617833@sss.pgh.pa.us
Whole thread Raw
In response to Re: Simplifying wal_sync_method  (Andrew - Supernews <andrew+nonews@supernews.com>)
List pgsql-hackers
Andrew - Supernews <andrew+nonews@supernews.com> writes:
> On 2005-08-09, "Magnus Hagander" <mha@sollentuna.net> wrote:
>> ... or iDE disks with write cache enabled. I've certainly seen more than
>> what I'd call 1% (though I haven't studied it to be sure) that's because
>> of write-cached disks...

> Every SCSI disk I've looked at recently has had write cache enabled by
> default, fwiw.

On SCSI, write cacheing is default because the protocol is actually
designed to support it: the drive can take the data, and then take some
more, without giving the impression that the write has been done.

If a SCSI drive reports write complete when it hasn't actually put the
bits on the platter yet, then it's simply broken.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: small proposal: pg_config record flag variables?
Next
From: Tom Lane
Date:
Subject: Re: small proposal: pg_config record flag variables?