Search Postgresql Archives

Re: Excessive (and slow) fsync() within single transaction

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Dec 9, 2009 at 2:35 PM, Ron Mayer <rm_pg@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
> Scott Marlowe wrote:
>> Actually, it's usually the drives that lie about fsync, especially
>> consumer grade (and some server grade) SATA / PATA drives are known
>> for this.
>
> I'm still looking for any evidence of any drive that lies.

I've tested drive in the past (when PATA roamed the land, and 80Gig
drives were huge) and could most certainly induce db corruption by
starting pgbench with -c 100, forcing a checkpoing, and then pulling
the plug.  Turning off the write cache (ok all cache I guess) on those
drives made them capable of surviving the power plug being pulled.

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux