Re: Maximum transaction rate

From: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
To: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
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 21:07:11
Message-ID: 49BEBF7F.1060306@kaltenbrunner.cc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Scott Marlowe wrote:
> 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.

I guess thats likely because most SCSI drives (at least back in the
days) had write caches turned off by default (whereas IDE drives had
them turned on).
The Linux kernel docs actually have some stuff on the barrier
implementation (
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob_plain;f=Documentation/block/barrier.txt;hb=HEAD)
which seems to explain some of the issues related to that.

Stefan

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Kostadin Solakov 2009-03-16 21:55:00 Re: PostgreSQL on Webmin
Previous Message Joachim Tranvåg 2009-03-16 21:03:11 Re: (0x0000274D/10061) on Install