From: | Greg Stark <gsstark(at)mit(dot)edu> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCHES] O_DIRECT for WAL writes |
Date: | 2005-06-22 19:25:00 |
Message-ID: | 87mzpiyz1v.fsf@stark.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Unfortunately, I cannot believe these numbers --- the near equality of
> fsync off and fsync on means there is something very wrong with the
> measurements. What I suspect is that your ATA drives are doing write
> caching and thus the "fsyncs" are not really waiting for I/O at all.
I wonder whether it would make sense to have an automatic test for this
problem. I suspect there are lots of installations out there whose admins
don't realize that their hardware is doing this to them.
It shouldn't be too hard to test a few hundred or even a few thousand fsyncs
and calculate the seek time. If it implies a rotational speed over 15kRPM then
you know the drive is lying and the data storage is unreliable.
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew - Supernews | 2005-06-22 19:31:19 | Re: pg_terminate_backend idea |
Previous Message | Tom Lane | 2005-06-22 18:39:28 | Re: pg_terminate_backend idea |
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2005-06-22 19:47:51 | Re: pl/pgsql: END verbosity |
Previous Message | Alvaro Herrera | 2005-06-22 17:53:21 | Re: pl/pgsql: END verbosity |