| From: | Greg Smith <greg(at)2ndquadrant(dot)com> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, jd(at)commandprompt(dot)com, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Steve Crawford <scrawford(at)pinpointresearch(dot)com>, pgsql-performance(at)postgresql(dot)org, Ben Chobot <bench(at)silentmedia(dot)com> |
| Subject: | Re: BBU Cache vs. spindles |
| Date: | 2010-10-21 17:31:09 |
| Message-ID: | 4CC078DD.3010107@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance pgsql-www |
Kevin Grittner wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
>
>> full_page_writes is designed to guard against a partial write to a
>> device. I don't think the raid cache can be partially written to
>>
>
> So you're confident that an 8kB write to the controller will not be
> done as a series of smaller atomic writes by the OS file system?
Sure, that happens. But if the BBU has gotten an fsync call after the
8K write, it shouldn't return success until after all 8K are in its
cache. That's why full_page_writes should be safe on a system with BBU
as Bruce is suggesting. But I'd like to see some independent proof of
that fact, that includes some targeted tests users can run, before we
start recommending that practice.
--
Greg Smith, 2ndQuadrant US greg(at)2ndQuadrant(dot)com Baltimore, MD
PostgreSQL Training, Services and Support www.2ndQuadrant.us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jesper Krogh | 2010-10-21 18:13:24 | Re: Slow count(*) again... |
| Previous Message | Kevin Grittner | 2010-10-21 17:15:15 | Re: BBU Cache vs. spindles |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua Tolley | 2010-10-21 18:04:01 | Doc search fail |
| Previous Message | Kevin Grittner | 2010-10-21 17:15:15 | Re: BBU Cache vs. spindles |