| From: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Dangers of fsync = off |
| Date: | 2007-05-08 14:09:21 |
| Message-ID: | 20070508140921.GG2735@phlogiston.dyndns.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, May 04, 2007 at 08:54:10AM -0600, Joel Dice wrote:
>
> My next question is this: what are the dangers of turning fsync off in the
> context of a high-availablilty cluster using asynchronous replication?
My real question is why you want to turn it off. If you're using a
battery-backed cache on your disk controller, then fsync ought to be
pretty close to free. Are you sure that turning it off will deliver
the benefit you think it will?
> on Y. Thus, database corruption on X is irrelevant since our first step
> is to drop them.
Not if the corruption introduces problems for replication, which is
indeed possible.
A
--
Andrew Sullivan | ajs(at)crankycanuck(dot)ca
A certain description of men are for getting out of debt, yet are
against all taxes for raising money to pay it off.
--Alexander Hamilton
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2007-05-08 15:15:48 | Re: Any "guide to indexes" exists? |
| Previous Message | Tom Lane | 2007-05-08 14:06:44 | Re: are foreign keys realized as indexes? |