Thanks, Bill and Scott, for your responses.
To summarize, turning fsync off on the master of a Slony-I cluster is
probably safe if you observe the following:
1. When failover occurs, drop all databases on the failed machine and
sync it with the new master before re-introducing it into the
Thanks for your response, Andrew.
On Tue, 8 May 2007, Andrew Sullivan wrote:
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
Thanks for the explanation, Tom. I understand the problem now.
My next question is this: what are the dangers of turning fsync off in the
context of a high-availablilty cluster using asynchronous replication?
In particular, we are using Slony-I and linux-ha to provide a two-node,
Hello all.
It's clear from the documentation for the fsync configuration option that
turning it off may lead to unrecoverable data corruption. I'd like to
learn more about why this is possible and how likely it really is.
A quick look at xlog.h reveals that each record in the transaction
