Message-ID: <528F4BE2.7000400@gmx.net>
Date: Fri, 22 Nov 2013 13:19:46 +0100
From: =?UTF-8?B?VG9yc3RlbiBGw7ZydHNjaA==?= <torsten.foertsch@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Albe Laurenz <laurenz.albe@wien.gv.at>,
 Kaushal Shriyan *EXTERN* <kaushalshriyan@gmail.com>,
 "pgsql-general@postgresql.org" <pgsql-general@postgresql.org>
Subject: Re: PG replication across DataCenters
References: 
 <CAD7Ssm9S__ZQCOq2GEN0G0rrs_4U6aqXiLaX0hh0Ts8JH_LY2w@mail.gmail.com>
 <A737B7A37273E048B164557ADEF4A58B17C5ED75@ntex2010i.host.magwien.gv.at>
In-Reply-To: 
 <A737B7A37273E048B164557ADEF4A58B17C5ED75@ntex2010i.host.magwien.gv.at>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-general-owner@postgresql.org

On 22/11/13 11:57, Albe Laurenz wrote:
> Don't use synchronous replication if you have a high transaction
> rate and a noticable network latency between the sites.
> 
> Wait for the next bugfix release, since a nasty bug has just
> been discovered.

Can you please explain or provide a pointer for more information?

We have recently started to use sync replication over a line with >80ms
latency. It works for small transactions with a relatively low
transaction rate.

Avoid transactions using NOTIFY. Those acquire an exclusive lock during
commit that is released only when the remote host has also done its
commit. So, only one such transaction can be committing at time.

Async replication works just fine.

Torsten


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general