| From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | DDT *EXTERN* <410845160(at)qq(dot)com>, maillists0 <maillists0(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Replication and fsync |
| Date: | 2013-10-25 09:25:50 |
| Message-ID: | A737B7A37273E048B164557ADEF4A58B17C52478@ntex2010i.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
DDT wrote:
> According to manual, when you set "synchronous_commit" to on, the transaction commits will wait until
> master and slave flush the commit record of transaction to the physical storage, so I think even if
> turn off the fsync on master is safe for data consistency and data will not be lost if slave physical
> storage is not damaged.
I don't think that this is safe.
What if the master crashes and becomes corrupted as a consequence?
It will start sending corrupted data to the slave, which will
replay it, thus becoming corrupted itself.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ivan Voras | 2013-10-25 10:42:06 | Re: "Recheck conditions" on indexes |
| Previous Message | Albe Laurenz | 2013-10-25 09:06:25 | Re: "Recheck conditions" on indexes |