Received: from localhost (unknown [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id 444B0650456
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Thu,  6 Nov 2008 18:45:59 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 61143-10
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Thu,  6 Nov 2008 18:45:58 -0400 (AST)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from wa-out-1112.google.com (wa-out-1112.google.com
 [209.85.146.179])
	by mail.postgresql.org (Postfix) with ESMTP id B1185650447
	for <pgsql-performance@postgresql.org>;
	Thu,  6 Nov 2008 18:45:58 -0400 (AST)
Received: by wa-out-1112.google.com with SMTP id j4so459690wah.19
	for <pgsql-performance@postgresql.org>;
	Thu, 06 Nov 2008 14:45:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references;
	bh=8ulDGGGl2hLZJjaQnGFb0XU9YG+HvgrOLpryN2xja28=;
	b=ZfKsJw6IKLbF4wwhZKESwebSpU+3mdF2Ol0QQQZGFh06G+TXFjw+QOGnSDGf8qXg9g
	dQqiDVpr7WMuV3jjH6bQarbh8WkC3bgRJLwElZ4bpi3letUUq+lrO3LQAlVnGKRup9UE
	5VpIs6wt3PGXDhUfwj/DOGEwt2iZaDWgu4tTo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=mfqeU9vbJ923fkAR78ntHvBbQe7RXrhCmZbbqKEjQBRmxV6L82p6ifEacN6YRAEeBv
	ixRUHOA11B3sRRz6bWGohJgLvsjC5m2NlCPPV/gBqyINfcy6aAHCIgIg3CL6nTf3INBD
	s1OWATgip0r7NAb98YO0hbPMavGAmozUYs+6s=
Received: by 10.114.37.3 with SMTP id k3mr1050348wak.98.1226011557289;
	Thu, 06 Nov 2008 14:45:57 -0800 (PST)
Received: by 10.114.39.11 with HTTP; Thu, 6 Nov 2008 14:45:57 -0800 (PST)
Message-ID: <dcc563d10811061445h32c5ad72o84f367d7cc3c6899@mail.gmail.com>
Date: Thu, 6 Nov 2008 15:45:57 -0700
From: "Scott Marlowe" <scott.marlowe@gmail.com>
To: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Subject: Re: Create and drop temp table in 8.3.4
Cc: "Scott Carey" <scott@richrelevance.com>, jd@commandprompt.com,
	pgsql-performance@postgresql.org
In-Reply-To: <49131C67.EE98.0025.0@wicourts.gov>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <4911957A.EE98.0025.0@wicourts.gov>
	<4911D4DB.EE98.0025.0@wicourts.gov>
	<4912EAFF.EE98.0025.0@wicourts.gov>
	<1225999071.1204.14.camel@jd-laptop.pragmaticzealot.org>
	<4912F29E.EE98.0025.0@wicourts.gov>
	<a1ec7d000811061305n7b28800od469c1411e1a9928@mail.gmail.com>
	<dcc563d10811061405l76cb59adh58741b227fe9d8a6@mail.gmail.com>
	<49131C67.EE98.0025.0@wicourts.gov>
X-Archive-Number: 200811/42
X-Sequence-Number: 31773

On Thu, Nov 6, 2008 at 3:33 PM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
>>>> "Scott Marlowe" <scott.marlowe@gmail.com> wrote:
>> I am pretty sure that with no write barriers that even a BBU
> hardware
>> caching raid controller cannot guarantee your data.
>
> That seems at odds with this:
>
> http://oss.sgi.com/projects/xfs/faq.html#wcache_persistent
>
> What evidence to you have that the SGI XFS team is wrong?

Logic?  Without write barriers in my file system an fsync request will
be immediately returned true, correct?  That means that writes can
happen out of order, and a system crash could corrupt the file system.
 Just seems kind of obvious to me.