a failover scenario

From: "Tomi N/A" <hefest(at)gmail(dot)com>
To: "postgres general" <pgsql-general(at)postgresql(dot)org>
Subject: a failover scenario
Date: 2007-10-18 10:15:44
Message-ID: d487eb8e0710180315w3b7262ccv5fd1c8917c445d71@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I am considering pgsql as the RDBMS in a project with the following constraints:
- there's a master and reserve instance of the RDBMS on every remote location
- there's a master and reserve instance of the RDBMS on a central location
- the connections are DSL connections and therefore unreliable
- all changes have to be propagated to all servers (multimaster replication)
- if the connection between a remote location and the central location
fails, the local server continues working and resynchronizes with the
central server when the connection is restored
- if any master fails, the reserve instance takes over and the rest of
the system acts as though nothing happened

The master/reserve instance is, from what I read, standard
functionality, but I'm not so sure about the resynchronization part of
a failed link...I imagine something like WAL shipping might be of use
here, but it's just an uneducated guess.
Does code exist to support this on pgsql or is it considered
application specific functionality? Do other RDBMSs support similar
functionality?

TIA,
t.n.a.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alvaro Herrera 2007-10-18 11:21:13 Re: Poor Plan selected w/ not provided a date/time but selecting date/time from a table
Previous Message jehan.procaccia 2007-10-18 09:23:02 Re: move databases files location