Re: Replication and fsync - Mailing list pgsql-general

From Alban Hertroys
Subject Re: Replication and fsync
Date
Msg-id CAF-3MvM_cAUP_yMn3F7JNDQY14zp5DGX3J9Y=-utP1W28nmKvg@mail.gmail.com
Whole thread Raw
In response to Re: Replication and fsync  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: Replication and fsync
List pgsql-general
On 24 October 2013 15:04, Fujii Masao <masao.fujii@gmail.com> wrote:
> On Thu, Oct 24, 2013 at 10:39 AM,  <maillists0@gmail.com> wrote:
>> Am I wrong? If I'm wrong, is there still danger to the slave
>> in this kind of setup?
>
> No, I think.

Corruption due to fsync being off on the master will be replicated to
the slave, or - if corruption is bad enough - replication will fail to
replicate affected records entirely. Of course, turning fsync off is
no guarantee for corruption - it's the other way around: having it on
guarantees that you don't get corruption (provided that... etc).

You could disable replication while fsync is off. I'd verify the data
on the master (by creating a dump, for example) before re-enabling it
again, though.

--
If you can't see the forest for the trees,
Cut the trees and you'll see there is no forest.


pgsql-general by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Replication and fsync
Next
From: Tom Lane
Date:
Subject: Re: GIST index : order Hack : getting the order used by CLUSTER .. USING my_index