| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | Greg Smith <greg(at)2ndquadrant(dot)com>, Craig James <craig_james(at)emolecules(dot)com>, Matthew Wakeling <matthew(at)flymine(dot)org>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Weird XFS WAL problem |
| Date: | 2010-06-03 19:10:12 |
| Message-ID: | AANLkTimBauZ7cZ5Ba78-a9KsaBO418xGJHFT0vGidK8A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, Jun 3, 2010 at 12:40 PM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
>
> Yeah, I read that long ago and I've disabled write barriers because
> of it; however, it still seems wrong that the RAID controller
> insists on flushing to the drives in write-back mode. Here are my
> reasons for wishing it was otherwise:
I think it's a case of the quickest, simplest answer to semi-new tech.
Not sure what to do with barriers? Just flush the whole cache.
I'm guessing that this will get optimized in the future.
BTW, I'll have LSI Megaraid latest and greatest to test on in a month,
and older Areca 1680s as well. I'll be updating the firmware on the
arecas, and I'll run some tests on the whole barrier behaviour to see
if it's gotten any better lately.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2010-06-03 19:17:28 | Re: Weird XFS WAL problem |
| Previous Message | Andy Colson | 2010-06-03 18:43:21 | Re: slow query performance |