| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jack Orenstein <jack(dot)orenstein(at)hds(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Maximum transaction rate |
| Date: | 2009-03-16 20:31:22 |
| Message-ID: | dcc563d10903161331p17741ab1ve62a68f12d5c5b06@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Mar 16, 2009 at 2:03 PM, Stefan Kaltenbrunner
<stefan(at)kaltenbrunner(dot)cc> wrote:
> So in my understanding LVM is safe on disks that have write cache disabled
> or "behave" as one (like a controller with a battery backed cache).
> For storage with write caches it seems to be unsafe, even if the filesystem
> supports barriers and it has them enabled (which I don't think all have)
> which is basically what all of linux was not too long ago.
I definitely didn't have this problem with SCSI drives directly
attached to a machine under pgsql on ext2 back in the day (way back,
like 5 to 10 years ago). IDE / PATA drives, on the other hand,
definitely suffered with having write caches enabled.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2009-03-16 20:32:40 | Re: Maximum transaction rate |
| Previous Message | Stefan Kaltenbrunner | 2009-03-16 20:22:36 | Re: deployment query |