| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Scott Carey" <scott(at)richrelevance(dot)com> |
| Cc: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>, jd(at)commandprompt(dot)com, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Create and drop temp table in 8.3.4 |
| Date: | 2008-11-06 22:05:21 |
| Message-ID: | dcc563d10811061405l76cb59adh58741b227fe9d8a6@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, Nov 6, 2008 at 2:05 PM, Scott Carey <scott(at)richrelevance(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2008-11-06 22:10:29 | Re: lru_multiplier and backend page write-outs |
| Previous Message | Kevin Grittner | 2008-11-06 21:49:59 | Re: Create and drop temp table in 8.3.4 |