From: Scott Marlowe <scott.marlowe@gmail.com>
To: Scott Carey <scott@richrelevance.com>
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: jd@commandprompt.com
Cc: pgsql-performance@postgresql.org
Subject: Re: Create and drop temp table in 8.3.4
Date: Thu, 6 Nov 2008 15:05:21 -0700
Message-ID: <dcc563d10811061405l76cb59adh58741b227fe9d8a6@mail.gmail.com> (raw)
In-Reply-To: <a1ec7d000811061305n7b28800od469c1411e1a9928@mail.gmail.com>
References: <4911957A.EE98.0025.0@wicourts.gov>
<4911D4DB.EE98.0025.0@wicourts.gov>
<4912EAFF.EE98.0025.0@wicourts.gov>
<1225999071.1204.14.camel@jd-laptop.pragmaticzealot.org>
<4912F29E.EE98.0025.0@wicourts.gov>
<a1ec7d000811061305n7b28800od469c1411e1a9928@mail.gmail.com>
On Thu, Nov 6, 2008 at 2:05 PM, Scott Carey <scott@richrelevance.com> wrote:
> To others that may stumble upon this thread:
> Note that Write Barriers can be very important for data integrity when power
> loss or hardware failure are a concern. Only disable them if you know the
> consequences are mitigated by other factors (such as a BBU + db using the
> WAL log with sync writes), or if you accept the additional risk to data
> loss. Also note that LVM prevents the possibility of using write barriers,
> and lowers data reliability as a result. The consequences are application
> dependent and also highly file system dependent.
I am pretty sure that with no write barriers that even a BBU hardware
caching raid controller cannot guarantee your data.
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: scott.marlowe@gmail.com, scott@richrelevance.com, Kevin.Grittner@wicourts.gov, jd@commandprompt.com
Subject: Re: Create and drop temp table in 8.3.4
In-Reply-To: <dcc563d10811061405l76cb59adh58741b227fe9d8a6@mail.gmail.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