| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Tomas Vondra <tv(at)fuzzy(dot)cz> |
| Cc: | Yan Chunlu <springrider(at)gmail(dot)com>, Scott Ribe <scott_ribe(at)elevated-dev(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: streaming replication does not work across datacenter with 20ms latency? |
| Date: | 2011-07-23 18:44:08 |
| Message-ID: | CAOR=d=1H+eEbsyp7HyEs8U1pV8QLOBzMvBwRsWBACGvVZ9rj-Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, Jul 23, 2011 at 11:55 AM, Tomas Vondra <tv(at)fuzzy(dot)cz> wrote:
> On 23 Červenec 2011, 18:14, Yan Chunlu wrote:
>> 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
>
> It is not just about the architecture, it means the PostgreSQL was
> configured somehow differently during the build. E.g. a different block
> size or WAL block size would make such problems.
>
> Or maybe one of the buils might be 32-bit for some reason (you can run
> 32-bit system in a 64-bit environment). You can do this
>
> $ less postgres | grep Class
>
> to check this (ELF32 => 32bit, ELF64 => 64bit).
>
> Did you use the same binary packages or have you built the server yourself?
Different date formats too.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2011-07-23 18:46:23 | Re: weird table sizes |
| Previous Message | MirrorX | 2011-07-23 18:29:48 | weird table sizes |