| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | maillists0(at)gmail(dot)com |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Replication and fsync |
| Date: | 2013-10-24 20:51:09 |
| Message-ID: | CAMkU=1y=URZpPfzP_gdnHOQNkFV3AsG_=WT+Cw59PnctBAPC3Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Oct 23, 2013 at 6:39 PM, <maillists0(at)gmail(dot)com> wrote:
> Newb question.
>
> I'm running 9.1 with a slave using streaming replication. A coworker wants
> to turn off fsync on the master and insists that the slave will still be in
> a usable state if there is a failure on the master.
>
This would only be safe if you made sure to shoot the master in the head
after a crash. If the master ever comes back up again, through automatic
recovery or through start-up scripts, it could start feeding corrupt WAL
records to the slave, corrupting it as well.
Cheers,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert James | 2013-10-24 21:09:45 | Re: Count of records in a row |
| Previous Message | Alan Hodgson | 2013-10-24 19:14:17 | Re: PostgreSQL Point In Time Recovery |