Re: Create and drop temp table in 8.3.4 - Mailing list pgsql-performance

From Scott Marlowe
Subject Re: Create and drop temp table in 8.3.4
Date
Msg-id dcc563d10811061445h32c5ad72o84f367d7cc3c6899@mail.gmail.com
Whole thread Raw
In response to Re: Create and drop temp table in 8.3.4  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: Create and drop temp table in 8.3.4  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-performance
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.

pgsql-performance by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: Create and drop temp table in 8.3.4
Next
From: Peter Schuller
Date:
Subject: Re: lru_multiplier and backend page write-outs