| From: | Torsten Förtsch <torsten(dot)foertsch(at)gmx(dot)net> |
|---|---|
| To: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, Kaushal Shriyan *EXTERN* <kaushalshriyan(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: PG replication across DataCenters |
| Date: | 2013-11-22 12:19:46 |
| Message-ID: | 528F4BE2.7000400@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Albe Laurenz | 2013-11-22 12:44:18 | Re: PG replication across DataCenters |
| Previous Message | Edson Richter | 2013-11-22 11:04:16 | Re: PG replication across DataCenters |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Albe Laurenz | 2013-11-22 12:44:18 | Re: PG replication across DataCenters |
| Previous Message | Edson Richter | 2013-11-22 11:04:16 | Re: PG replication across DataCenters |