| From: | Ondrej Ivanič <ondrej(dot)ivanic(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Cc: | John R Pierce <pierce(at)hogranch(dot)com> |
| Subject: | Re: replication between US <-> EU |
| Date: | 2012-03-07 00:12:58 |
| Message-ID: | CAM6mie+as=ZN2UMs=inTKTE-RnEe18yZ93ym+cwWWW9V8M=VSg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
On 7 March 2012 10:36, John R Pierce <pierce(at)hogranch(dot)com> wrote:
> On 03/06/12 3:31 PM, Ondrej Ivanič wrote:
>>
>> - one side completely down: Client should use switch to other side
>> transparently (Failover / High Availability)
>
>
> what happens if the link between the sites is down and both sides decide
> they are master? then how do you put the pieces back together ?
Good catch! From application point of it is quite easy to sync data
between sites. Let's assume that writes should be disabled in this
scenario.
--
Ondrej Ivanic
(ondrej(dot)ivanic(at)gmail(dot)com)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matteo Sgalaberni | 2012-03-07 00:34:32 | Re: corrupted table postgresql 8.3 |
| Previous Message | Tom Lane | 2012-03-07 00:09:48 | Re: Single server multiple databases - extension |