| From: | Greg Smith <greg(at)2ndquadrant(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, jd(at)commandprompt(dot)com, Ben Chobot <bench(at)silentmedia(dot)com>, Steve Crawford <scrawford(at)pinpointresearch(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: BBU Cache vs. spindles |
| Date: | 2010-10-21 17:04:17 |
| Message-ID: | 4CC07291.8020601@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance pgsql-www |
Bruce Momjian wrote:
> With a BBU you can turn off full_page_writes, which should decrease the
> WAL traffic.
>
> However, I don't see this mentioned in our documentation. Should I add
> it?
>
What I would like to do is beef up the documentation with some concrete
examples of how to figure out if your cache and associated write path
are working reliably or not. It should be possible to include "does
this handle full page writes correctly?" in that test suite. Until we
have something like that, I'm concerned that bugs in filesystem or
controller handling may make full_page_writes unsafe even with a BBU,
and we'd have no way for people to tell if that's true or not.
--
Greg Smith, 2ndQuadrant US greg(at)2ndQuadrant(dot)com Baltimore, MD
PostgreSQL Training, Services and Support www.2ndQuadrant.us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2010-10-21 17:15:15 | Re: BBU Cache vs. spindles |
| Previous Message | Bruce Momjian | 2010-10-21 16:59:46 | Re: BBU Cache vs. spindles |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2010-10-21 17:15:15 | Re: BBU Cache vs. spindles |
| Previous Message | Bruce Momjian | 2010-10-21 16:59:46 | Re: BBU Cache vs. spindles |