Re: Create and drop temp table in 8.3.4

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
Cc: <jd(at)commandprompt(dot)com>,<pgsql-performance(at)postgresql(dot)org>, "Scott Carey" <scott(at)richrelevance(dot)com>
Subject: Re: Create and drop temp table in 8.3.4
Date: 2008-11-06 23:04:03
Message-ID: 49132383.EE98.0025.0@wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

>>> "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> wrote:
> On Thu, Nov 6, 2008 at 3:33 PM, Kevin Grittner
> <Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
>>>>> "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)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?
>
> Without write barriers in my file system an fsync request will
> be immediately returned true, correct?

Not as I understand it; although it will be pretty fast if it all fits
into the battery backed cache.

-Kevin

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Scott Marlowe 2008-11-07 00:03:58 Re: Create and drop temp table in 8.3.4
Previous Message Peter Schuller 2008-11-06 23:04:01 Re: lru_multiplier and backend page write-outs