Re: Options for fsync?

From: Greg Smith <greg(at)2ndquadrant(dot)com>
To: A B <gentosaker(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Options for fsync?
Date: 2010-03-15 13:02:13
Message-ID: 4B9E2FD5.3070700@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

A B wrote:
> If I had a controller with battery, then I could use fsync=off, but I
> should still disable the write cache?
>

Never turn fsync=off. Always disable any write cache on the drives
themselves; most good battery-backed RAID controllers will do that for
you. So long as the battery continues to work, you can keep the write
cache on the controller itself enabled, and in fact you have to do so in
order to get good commit performance. Given that eventually all
batteries fail, the better cards on the market actually make that an
explicit setting, which is the safest setting if available: write-back
cache enabled when battery works, write-through [cache disabled] if doesn't.

Make sure you setup monitoring alerts via e-mail for drive and battery
failures too; test them out by yanking at drive before the server goes
into production if you can.

--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services and Support
greg(at)2ndQuadrant(dot)com www.2ndQuadrant.us

In response to

Browse pgsql-general by date

  From Date Subject
Next Message A. Kretschmer 2010-03-15 13:16:37 Re: Unable to connect to Postgres database from email marketing software on the same host
Previous Message Major Services 2010-03-15 12:55:55 Re: Unable to connect to Postgres database from email marketing software on the same host