From: Greg Smith <greg@2ndquadrant.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: Scott Marlowe <scott.marlowe@gmail.com>
Cc: jd@commandprompt.com, Ben Chobot <bench@silentmedia.com>
Cc: Steve Crawford <scrawford@pinpointresearch.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: BBU Cache vs. spindles
Date: Thu, 21 Oct 2010 13:04:17 -0400
Message-ID: <4CC07291.8020601@2ndquadrant.com> (raw)
In-Reply-To: <201010211651.o9LGp9I28474@momjian.us>
References: <201010211651.o9LGp9I28474@momjian.us>
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@2ndQuadrant.com Baltimore, MD
PostgreSQL Training, Services and Support www.2ndQuadrant.us
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: greg@2ndquadrant.com, bruce@momjian.us, scott.marlowe@gmail.com, bench@silentmedia.com, scrawford@pinpointresearch.com
Subject: Re: BBU Cache vs. spindles
In-Reply-To: <4CC07291.8020601@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox