| From: | Samrat Revagade <revagade(dot)samrat(at)gmail(dot)com> |
|---|---|
| To: | Hannu Krosing <hannu(at)2ndquadrant(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, sthomas(at)optionshouse(dot)com, ants(at)cybertec(dot)at, andres(at)2ndquadrant(dot)com |
| Subject: | Re: Inconsistent DB data in Streaming Replication |
| Date: | 2013-04-10 10:11:54 |
| Message-ID: | CAF8Q-GwjduHPwERW4jewX8CkVCk6PWeMmdENBiJLo+R6-9Vi+w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>(5) *The master then forces a write of the data page related to this
transaction.*
*Sorry, this is incorrect. Whenever the master writes the data page it
checks that the WAL record is written in standby till that LSN. *
*
*
>While master is waiting to force a write (point 5) for this data page,
streaming replication continuous.
>Also other data page writes are not dependent on this particular page
write. So the commit of data >pages are not serialized.
*Sorry, this is incorrect. Streaming replication continuous, master is not
waiting, whenever the master writes the data page it checks that the WAL
record is written in standby till that LSN.*
*
*
*Regards,*
*Samrat*
*
*
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ants Aasma | 2013-04-10 10:15:12 | Re: Enabling Checksums |
| Previous Message | Dang Minh Huong | 2013-04-10 09:57:41 | Re: replication_timeout not effective |