From: | Yan Chunlu <springrider(at)gmail(dot)com> |
---|---|
To: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: streaming replication does not work across datacenter with 20ms latency? |
Date: | 2011-07-23 16:14:51 |
Message-ID: | CAOA66tERKkB25tuLU=ehmYDm-SYKZ5nobdtT+W=d+geF1k=eHQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
thanks for the help!
are there any other possible reasons?
both system are using Debian amd64, as uname -a shows:
Linux washington 2.6.26-2-amd64 #1 SMP Tue Mar 9 22:29:32 UTC 2010
x86_64 GNU/Linux
and using the following program it tells both of them are little-endian
#include <stdio.h>
#include <stdbool.h>
bool isBigEndian()
{
int no = 1;
char *chk = (char *)&no;
if (chk[0] == 1)
{
return 0;
}
else
{
return 1;
}
}
main()
{
printf("this is %d \n",(int)isBigEndian());
return 0;
}
~
On Sat, Jul 23, 2011 at 11:55 PM, Scott Ribe
<scott_ribe(at)elevated-dev(dot)com> wrote:
> On Jul 23, 2011, at 6:50 AM, Yan Chunlu wrote:
>
>> what does invalid record length and invalid magic number normally
>> means? xlog corrupted?
>> Thanks for any further help!
>
> It means your build settings for pg are not compatible across the 2 machines. For instance, one machine is 32-bit and the other is 64-bit, or one machine is big-endian and the other is little-endian...
>
> --
> Scott Ribe
> scott_ribe(at)elevated-dev(dot)com
> http://www.elevated-dev.com/
> (303) 722-0567 voice
>
>
>
>
>
--
闫春路
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2011-07-23 16:31:30 | Re: Question about uuid_generate_v3 |
Previous Message | Ilia Lilov | 2011-07-23 16:01:47 | Re: Locking several tables within one transaction |