From: Tom Lane <tgl@sss.pgh.pa.us>
To: Joost Kraaijeveld <J.Kraaijeveld@Askesis.nl>
Cc: PFC <lists@peufeu.com>
Cc: David Lang <david@lang.hm>
Cc: Richard Huxton <dev@archonet.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: x206-x225
Date: Sat, 11 Mar 2006 11:59:29 -0500
Message-ID: <28030.1142096369@sss.pgh.pa.us> (raw)
In-Reply-To: <1142087174.6634.32.camel@localhost>
References: <GMEAJIDMNDKCIHMMHDFLCEKHDHAA.hjs@rmax.nl>
<441181C6.3040401@archonet.com>
<1142063378.6634.13.camel@localhost>
<Pine.LNX.4.62.0603102355550.23148@qnivq.ynat.uz>
<1142065029.6634.23.camel@localhost>
<op.s58yeob1cigqcu@apollo13>
<1142087174.6634.32.camel@localhost>
Joost Kraaijeveld <J.Kraaijeveld@Askesis.nl> writes:
> I assume that for PostgreSQL "written to disk" is after fsync returned
> successfully. In practice that could very well mean that the data is
> still in a cache somewhere (controller or harddisk, not in the OS
> anymore, see also man page of fsync)
What it had better mean, if you want your database to be reliable,
is that the data is stored someplace that will survive a system crash
(power outage, kernel panic, etc). A battery-backed RAM cache is OK,
assuming that total failure of the RAID controller is not one of the
events you consider likely enough to need protection against.
The description of your SATA drive makes it sound like the drive
does not put data on the platter before reporting "write complete",
but only stores it in on-board RAM cache. It is highly unlikely
that there is any battery backing for that cache, and therefore that
drive is not to be trusted.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, J.Kraaijeveld@Askesis.nl, lists@peufeu.com, david@lang.hm, dev@archonet.com
Subject: Re: x206-x225
In-Reply-To: <28030.1142096369@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox