Re: streaming replication does not work across datacenter with 20ms latency?

sorry for the typo, "debian and apt-get"

On Mon, Jul 25, 2011 at 5:39 PM, Yan Chunlu <springrider(at)gmail(dot)com> wrote:
> I am using debian and apt-get to install postgresql, dpkg list shows
> they are the same?  is there anyway to tell what's version it is
> compiled from? thanks!
>
> Master# dpkg -l |grep post
> ii  postgresql-9.0                      9.0.4-1+b1
>  object-relational SQL database, version 9.0 server
> ii  postgresql-client-9.0               9.0.4-1+b1
>  front-end programs for PostgreSQL 9.0
> ii  postgresql-client-common            118
>  manager for multiple PostgreSQL client versions
> ii  postgresql-common                   118
>  PostgreSQL database-cluster manager
> ii  postgresql-contrib-9.0              9.0.4-1+b1
>  additional facilities for PostgreSQL
> ii  postgresql-server-dev-9.0           9.0.4-1+b1
>  development files for PostgreSQL 9.0 server-side programming
>
>
> Slave $ dpkg -l |grep post
> ii  postgresql-9.0                      9.0.4-1+b1
> object-relational SQL database, version 9.0 server
> ii  postgresql-client-9.0               9.0.4-1+b1
> front-end programs for PostgreSQL 9.0
> ii  postgresql-client-common            118
> manager for multiple PostgreSQL client versions
> ii  postgresql-common                   118
> PostgreSQL database-cluster manager
> ii  postgresql-contrib-9.0              9.0.4-1+b1
> additional facilities for PostgreSQL
>
>
>
> On Mon, Jul 25, 2011 at 3:38 PM, 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 problem was fixed, and the fix will be included in next minor
>> update (i.e., 9.0.5).
>> http://archives.postgresql.org/pgsql-committers/2011-06/msg00101.php
>>
>> Of course, you can avoid the problem by building PostgreSQL with
>> gcc != 4.6.0, I think.
>>
>> Regards,
>>
>> --
>> Fujii Masao
>> NIPPON TELEGRAPH AND TELEPHONE CORPORATION
>> NTT Open Source Software Center
>>
>