From: | Alban Hertroys <haramrae(at)gmail(dot)com> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
Cc: | maillists0(at)gmail(dot)com, PostgreSQL pg-general List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Replication and fsync |
Date: | 2013-10-24 13:42:31 |
Message-ID: | CAF-3MvM_cAUP_yMn3F7JNDQY14zp5DGX3J9Y=-utP1W28nmKvg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 24 October 2013 15:04, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> On Thu, Oct 24, 2013 at 10:39 AM, <maillists0(at)gmail(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2013-10-24 13:42:54 | Re: GIST index : order Hack : getting the order used by CLUSTER .. USING my_index |
Previous Message | Fujii Masao | 2013-10-24 13:04:45 | Re: Replication and fsync |