| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Ron Mayer" <rm_pg(at)cheapcomplexdevices(dot)com> |
| Cc: | "Scott Carey" <scott(at)richrelevance(dot)com>, "Greg Smith" <gsmith(at)gregsmith(dot)com>, Henrik <henke(at)mac(dot)se>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Filesystem benchmarking for pg 8.3.3 server |
| Date: | 2008-08-13 07:03:29 |
| Message-ID: | dcc563d10808130003j37c71237q44e15859aedf391a@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, Aug 12, 2008 at 10:28 PM, Ron Mayer
<rm_pg(at)cheapcomplexdevices(dot)com> wrote:
> Scott Marlowe wrote:
>>
>> I can attest to the 2.4 kernel not being able to guarantee fsync on
>> IDE drives.
>
> Sure. But note that it won't for SCSI either; since AFAICT the write
> barrier support was implemented at the same time for both.
Tested both by pulling the power plug. The SCSI was pulled 10 times
while running 600 or so concurrent pgbench threads, and so was the
IDE. The SCSI came up clean every single time, the IDE came up
corrupted every single time.
I find it hard to believe there was no difference in write barrier
behaviour with those two setups.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthew Wakeling | 2008-08-13 10:15:55 | Re: Filesystem benchmarking for pg 8.3.3 server |
| Previous Message | Greg Smith | 2008-08-13 06:17:44 | Re: Filesystem benchmarking for pg 8.3.3 server |