| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Yan Chunlu <springrider(at)gmail(dot)com>, Tomas Vondra <tv(at)fuzzy(dot)cz>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: streaming replication does not work across datacenter with 20ms latency? |
| Date: | 2011-07-25 08:03:31 |
| Message-ID: | CA+U5nMJHvOXMGuict1juqtTphAoUGHKU-4dgzaFaOBNV=KWs1Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Jul 25, 2011 at 8:38 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> On Mon, Jul 25, 2011 at 10:56 AM, Yan Chunlu <springrider(at)gmail(dot)com> wrote:
>> I think the problem is still "invalid record length" and "invalid
>> magic number", it start showing right after I complete sync data and
>> start slave. If I stop slave later and restart, yes it could show
>> xlog not found and can not catch master. but why the "invalid" things
>> in the first place?
>
> You might have the same problem which was reported before.
> http://archives.postgresql.org/pgsql-hackers/2011-06/msg00661.php
That's what it looks like to me also.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Frank Lanitz | 2011-07-25 08:06:56 | Re: Implementing "thick"/"fat" databases |
| Previous Message | Markus Wollny | 2011-07-25 07:56:41 | Query, usually running <300ms, sometimes hangs for hours |